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(core): not parse hex to number #27515

Merged
merged 1 commit into from
Aug 23, 2024
Merged

Conversation

xiongemi
Copy link
Collaborator

Current Behavior

Expected Behavior

Related Issue(s)

Fixes #26889

@xiongemi xiongemi requested a review from a team as a code owner August 19, 2024 17:17
Copy link

vercel bot commented Aug 19, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Visit Preview Aug 23, 2024 2:58pm

@xiongemi xiongemi changed the title fix(core): fix not parse hex to number fix(core): not parse hex to number Aug 19, 2024
@@ -214,6 +216,8 @@ export function withRunManyOptions<T>(
'strip-dashed': true,
'unknown-options-as-args': true,
'populate--': true,
'parse-numbers': false,
'parse-positional-numbers': false,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel like other stuff will break with this... what about like --maxWarnings 5 or --parallel 8? 👀

Did you check those?

Copy link
Collaborator Author

@xiongemi xiongemi Aug 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i test it out:

  • for yargs option with type number (e.g. maxParallel), it is nx args, it will be converted as number.'parse-numbers': false, will be applied to for non-nx override options (e.g. _: [ '--max-warnings', '4', '--tag', '81919e4' ],
  • for parallel, the yargs option is string, however, there is a function readParallelFromArgsAndEnv that will do the parsing (
    export function readParallelFromArgsAndEnv(args: { [k: string]: any }) {
    )
    it will parse string to number inside that function
  • for the non nx args that is going to pass to executor, there is additional parsing in function createOverrides (
    export function createOverrides(__overrides_unparsed__: string[] = []) {
    ) which does not have 'parse-numbers': false,, so it will parse the args like maxWarnings to number: overrides: { 'max-warnings': 4, tag: 819190000, __overrides_unparsed__: [ '--max-warnings', '4', '--tag', '81919e4' ] },

in summary, this 'parse-numbers': false, will only be applied to non-nx override options, but not when it got passed to executor

@FrozenPandaz FrozenPandaz merged commit ec53f31 into master Aug 23, 2024
6 checks passed
@FrozenPandaz FrozenPandaz deleted the fix/fix-parse-hex-args branch August 23, 2024 21:20
FrozenPandaz pushed a commit that referenced this pull request Aug 26, 2024
<!-- Please make sure you have read the submission guidelines before
posting an PR -->
<!--
https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr
-->

<!-- Please make sure that your commit message follows our format -->
<!-- Example: `fix(nx): must begin with lowercase` -->

<!-- If this is a particularly complex change or feature addition, you
can request a dedicated Nx release for this pull request branch. Mention
someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they
will confirm if the PR warrants its own release for testing purposes,
and generate it for you if appropriate. -->

## Current Behavior
<!-- This is the behavior we have today -->

## Expected Behavior
<!-- This is the behavior we should expect with the changes in this PR
-->

## Related Issue(s)
<!-- Please link the issue being fixed so it gets closed when this is
merged. -->

Fixes #26889

(cherry picked from commit ec53f31)
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Unexpected number conversion of command line args
2 participants