Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Because
TxAuxData
isn't really used in the ledger rules it has been neglected whenever we did the refactor of the ledger interface using lenses.Now that we expanding our testing and have a need for era agnostic type construction we could use the same interface for
TxAuxData
as for other type families in ledger.This PR introduces:
Cardano.Ledger.Metadata
module withMetadatum
type moved to it fromcardano-ledger-shelley
mkBasicTxAuxData
andmetadataTxAuxDataL
toEraTxAuxData
type class.AllegraEraTxAuxData
type class withtimelockScriptsTxAuxDataL
lensAlonzoEraTxAuxData
type class withplutusScriptsTxAuxDataL
lensChecklist
.cabal
andCHANGELOG.md
files according to theversioning process.
.cabal
files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)CHANGELOG.md
for the affected packages. New section is never added with the code changes. (See RELEASING.md)fourmolu
(usescripts/fourmolize.sh
)scripts/cabal-format.sh
)hie.yaml
has been updated (usescripts/gen-hie.sh
)