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.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qmk format-json
: Add an in-place mode to format json command #21610qmk format-json
: Add an in-place mode to format json command #21610Changes from 1 commit
8b73c6f
d2d82aa
539ee8a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like with
--inplace
it would both write the formatted JSON back into the file and print the same JSON to stdout; is this intended and useful?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes - I didn't want to remove the stdout output as to maintain as much parity with existing functionality as possible.
If you think it's better to be removed, it's a trivial change to make.
In terms of usefulness - I suppose it could be useful as a gut-check for someone to look at after the command runs, but they can also just do a
git diff
or open the formatted info.json.Happy to do whichever the QMK team wants.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
imo, returning something like
qmk format-c
is doing by default https://github.com/qmk/qmk_firmware/blob/develop/lib/python/qmk/cli/format/c.py#L60 would probably be preferred to standardize on output and function . maybe do a-v
or-p
option to verbose/output in terminal. Up to QMK team for sure, thanks for the PR 👍There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dexter93 I think that approach is really nice, I'll implement it. Hopefully the QMK team likes it!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I looked again - I realized that the format-c command seems to run in-place and modify the file by default. Setting --dry-run causes the output to be print to stdout.
Given format-json already has different default behavior, and changing it to run in-place without printing could break user expectations - I think adding the --print flag is still the right call.