-
Notifications
You must be signed in to change notification settings - Fork 3
Comments
feat: add --json output flag to canister call#356
Draft
Conversation
Member
Author
marc0olo
commented
Feb 13, 2026
converted this into a draft because that might also be relevant for input formats and we can have different formats.
currently we always assume that Candid is returned.
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.
Summary
--jsonflag toicp canister callthat outputs the response as JSON instead of Candid text format, using theidl2jsoncrate (same approach as dfx)--jsonflag oncanister statusandnetwork status