Skip to content
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

fix: format program option #316

Merged
merged 1 commit into from
Mar 14, 2022
Merged

fix: format program option #316

merged 1 commit into from
Mar 14, 2022

Conversation

pomali
Copy link
Contributor

@pomali pomali commented Dec 19, 2021

index.js - options variable in parser() was overshadowing options
variable from main()

Q A
Branch? main for features / current stable version branch for bug fixes
Tickets
License MIT

L94 was using options.format from parser - which was always undefined

index.js - options variable in parser was overshadowing options
variable from main
@dunglas dunglas merged commit b993f82 into api-platform:main Mar 14, 2022
@dunglas
Copy link
Member

dunglas commented Mar 14, 2022

Thanks!

Sirs0ri added a commit to Sirs0ri/client-generator that referenced this pull request Apr 14, 2022
…platform#316)

In attempting to fix an empty `options` object overshadowing the options set by the user via CLI, api-platform#316 mistakenly adjusted `options.username`, `options.password` and `options.bearer` to be attributes of the newly introduced `parserOptions`. They should, however, still refer to the `options` object that holds all the information previously set via CLI arguments.
I also added two comments to make the difference between the two sets of options more clear.
Sirs0ri added a commit to Sirs0ri/client-generator that referenced this pull request Apr 14, 2022
…platform#316)

In attempting to fix an empty `options` object overshadowing the options set by the user via CLI, api-platform#316 mistakenly adjusted `options.username`, `options.password` and `options.bearer` to be attributes of the newly introduced `parserOptions`. They should, however, still refer to the `options` object that holds all the information previously set via CLI arguments.
I also added two comments to make the difference between the two sets of options more clear.
alanpoulain pushed a commit that referenced this pull request Apr 14, 2022
#325)

In attempting to fix an empty `options` object overshadowing the options set by the user via CLI, #316 mistakenly adjusted `options.username`, `options.password` and `options.bearer` to be attributes of the newly introduced `parserOptions`. They should, however, still refer to the `options` object that holds all the information previously set via CLI arguments.
I also added two comments to make the difference between the two sets of options more clear.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants