[FIX] JSON.stringify contract output #21
Open
Conversation
This file contains 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
Right now, some contract calls (like `gov staker <address>`), will output nested objects that don't correctly render. This ensures that all values are correctly rendered to the end user. Tested locally.
- Updated various calls so that the app compiles - Updated `rootDir` so that I can pull the version from package.json - `anchorcli -V` now returns a useful version
These files were automatically changed during a pre-commit hook
|
This is critical to facilitate interaction between the |
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.
Right now, some contract calls (like
gov staker <address>), willoutput nested objects that don't correctly render. This ensures that all
values are correctly rendered to the end user.
Tested locally.