view-user: make "parsable" spelling consistent
#494
Merged
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
Problem: There are multiple --parsable optional arguments throughout the flux-accounting command suite, but the spelling for it in the view-user command is not consistent and is spelled --parseable. Technically, both spellings are correct, but they should be made consistent throughout the command suite. Change the spelling of the --parseable optional argument for view-user to --parsable.
wihobbs
approved these changes
Oct 7, 2024
There was a problem hiding this comment.
Indeed you are correct: https://www.oed.com/dictionary/parsable_adj?tab=factsheet#32035960
|
thanks @wihobbs - setting MWP here |
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.
Problem
There are multiple
--parsableoptional arguments throughout the flux-accounting command suite, but the spelling for it in the view-user command is not consistent and is spelled--parseable. Technically, both spellings are correct, but they should be made consistent throughout the command suite.This PR just changes the spelling of the
--parseableoptional argument forview-userto--parsable.