fix: ABI generation#146
Merged
Merged
Conversation
Collaborator
|
Maybe other types should be reworked as well? |
Collaborator
Author
As I checked, these are the only types exposed in ABI. All other custom types in this crate are needed for events, which are not included in ABI |
This was referenced Mar 27, 2026
Closed
Closed
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.
This PR fixes an issue when ABI generation fails due to absence of
#[derive(JsonSchema)]Basically, in order to properly handle ABI generation via
cargo near, you're literally forced to use#[near(serializers = [json])], as its expanded version depends onnear-sdk/abifeature, so you can think of expanded version as: