Correct usage of terms "ABI" and "JSON ABI" #4847
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.
This PR clears up usage of terms "ABI" (our actual ABI) and "JSON ABI" (the JSON representation of our ABI).
What we really actually have here is the "Rust ABI" but we can drop the "Rust" and just call it "ABI".
Other ABIs would be the "TypeScript ABI" generated by fuels-ts, and the "GraphQL ABI" I'm planning to work on.