You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ingest/change Change struct has a field for Ledger *xdr.LedgerCloseMeta found here
It is not always populated depending on the Change.Reason (because LCM can be populated inside the change.Transaction). I believe it is more beneficial to always populate Change.Ledger no matter the change reason as it will always be able to be associated with a LedgerCloseMeta.
Supplementally we should evaluate whether or not it makes sense to always propagate OperationIndex and Transaction as well if they exist. This will depend on if they are only available for their correlated Change.Reason or if their current scope is not all inclusive of valid OperationIndex/Transaction data
Edit: OperationIndex and Transaction are always populated when relevant as it is already
The text was updated successfully, but these errors were encountered:
The ingest/change
Change
struct has a field forLedger *xdr.LedgerCloseMeta
found hereIt is not always populated depending on the Change.Reason (because LCM can be populated inside the change.Transaction). I believe it is more beneficial to always populate Change.Ledger no matter the change reason as it will always be able to be associated with a LedgerCloseMeta.
Supplementally we should evaluate whether or not it makes sense to always propagate OperationIndex and Transaction as well if they exist. This will depend on if they are only available for their correlated Change.Reason or if their current scope is not all inclusive of valid OperationIndex/Transaction data
Edit: OperationIndex and Transaction are always populated when relevant as it is already
The text was updated successfully, but these errors were encountered: