Fix: IDL gen byte string lit parsing #2125
Merged
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.
Byte strings were not being parsed properly due to the
match
statement not catching synLit
s. This PR adds a pattern to catch and parse these.Current build behavior with
seeds=true
:WARNING: unexpected seed: Lit(ExprLit { attrs: [], lit: ByteStr(LitByteStr { token: b"some string" }) })
This will turn the entire seed into
None
if a seeds group contains a byte string literal. In other words, the entire PDA object will be missing in the IDL.With the fix, the warning is gone and IDLs are generated as they should be.