This repository has been archived by the owner on Jan 10, 2025. It is now read-only.
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.
As explained in #7549,
InitializeMint
andInitializeMint2
without FreezeAuthority breakdecodeInitializeMintInstruction
anddecodeInitializeMint2Instruction
respectively.Since buffer layouts apparently don't support optional fields, this is currently a workaround. Indeed, this solution won't scale well when more than one optional field is present as it would require implementing the same logic for each combination of presence of each optional field.
The actual solution would require supporting optional
Layout
s inbuffer-layouts
, adapt theStructure
layout to account for it and easily provide a list of spans, then re-implementCOptionPublicKeyLayout
with it and check indecodeInitializeMintInstruction
anddecodeInitializeMint2Instruction
if the length of the buffer is in one of the values of spans provided byStructure
.Overall, I'd recommend not allowing optional fields, but rather have then set to a null value like 0 or -1.