Repository navigation
refactor(uplc): remove three casts left by #667 and #702 - #720
Merged
Merged
Conversation
This was referenced Oct 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
#667 and #702 left three type casts that compile without them: the array payload in
encodeData, the Value payload inconstantToJSON, and the program version passed toencodeTerm. #667 also adds the publicValueConstanttype and widensDataTypeandConstantValue, but its changeset says patch.This removes the three casts. An array constant without
itemsnow fails to encode with aUPLCErrorinstead of aTypeError. The #667 changeset moves to minor and mentions array payloads.