Fix transTxCert always setting deposit to Nothing for TxCertRegStaking & TxCertUnRegStaking #4542
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.
Doing some testing on my end, I noticed that deposits were always missing from TxCertRegStaking & TxCertUnRegStaking. However, they ought to be
Just
something when present; or more specifically when mapping aConwayRegCert
orConwayUnRegCert
to their Plutus counterpart.The deposit should, in principle, only be set to zero when presented with a legacy certificate format. However, if we take the following certificate:
Using
transTxCert
we obtain:And similarly for
ConwayUnRegCert
. This seems due to the order of clauses in the pattern match insidetransTxCert
which causesRegTxCert
andUnRegTxCert
to be matched even in the presence of a deposit. Swapping the pattern match clauses fixes the issue and return:The writing of a regression test to capture this is left as an excercise for the maintainers 😬
Description
Checklist
CHANGELOG.md
for the affected packages.New section is never added with the code changes. (See RELEASING.md)
.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)
fourmolu
(usescripts/fourmolize.sh
)scripts/cabal-format.sh
)hie.yaml
has been updated (usescripts/gen-hie.sh
)