-
Notifications
You must be signed in to change notification settings - Fork 500
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Include operation information in the ingest.Change struct (#5536)
This squash commit is the sum total of all the commits for this github issue - #5535 TL;dr Extend the ingest.Change struct to include information about the reason for the state change in the ledgerEntry. * Include operation information in the Change struct * Dont error out when operation index out of range * Fix failing unit test * Reafactor ledger_transaction.GetChanges() to use internal functions * reformat comments * Add all types of change reasons to the Change struct. Simplify LedgerTransaction.GetChanges() * Add LCM and transaction info altogether in change entry * Wrte help doc for Change Entry * Add TxHash to LedgerTransaction struct * reorg comments * Comments cleanup * Address PR review changes * rename fields * uncommit half baked changes * Add helpers in intergration tests for creating captive core config * fix updates to change struct * Updates to integration.go * Integration tests for change - part 1 * Undo all changes to parameters_test.go * Make updates to comments and rename variables * - Several changes to integration.go to pull out common functions from parameters_test.go to configure captive core - Add flags to capture state for upgrade version in test. - Add support to skip container deletion for debugging - Add test for upgrade related changes * cosmetic doc style changes * check err before file close * Add tx test and in change_test.go * code cleanup * Rework test fixtures * reformat file * Fix breaking test * Address code review comments
- Loading branch information
1 parent
969db99
commit 9b89f4b
Showing
8 changed files
with
534 additions
and
131 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.