[thekhegay]

PR Checklist

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

My library ngwr ships page schematic with two positionals, preset at index 0 (required, has x-prompt) and name at index 1
Command from its docs fails on 22.2.3:

$ ng g ngwr:page form signup
Error: Invalid values:
  Argument: preset, Given: "signup", Choices: "dashboard", "form", "table"

Help prints page [name] [preset]

Sort at end of parseJsonSchemaToOptions checks a.positional for truthiness, so index 0 is ordered like plain option and lands after index 1, and generate builds its comand string from that order
With x-prompt both positionals are optional for yargs and values get swapped, without it only help order is wrong since yargs fills <required> first

What is the new behavior?

Positionals are sorted by index (checked with !== undefined), plain options stay sorted by name after them
ng g ngwr:page form signup works and help prints page [preset] [name]

New case in json-schema_spec.ts has preset at index 0 with x-prompt and name at index 1, it fails on main
Also added fake-reversed schematic to generate/help-output.ts e2e, it gets [a] <b> on main
Existing <a> [b] case passes on main only becasue index order and alphabetical order are same there

Does this PR introduce a breaking change?

• Yes
• No

Other information

In @schematics/angular only interface has two positionals (name 0, type 1), they already sort same way, so nothing changes there
Built CLI from this branch and ran documented ngwr:page commands with --dry-run, all pass

[gemini-code-assist]

Code Review

This pull request fixes a bug in the JSON schema option parser where positional arguments with an index of 0 were incorrectly sorted because 0 is falsy. The sorting logic has been updated to explicitly check for undefined rather than relying on truthiness. Additionally, unit and E2E tests have been added to verify that positional arguments are sorted correctly by their index. There are no review comments, and I have no feedback to provide.

[alan-agius4]

LGTM

[clydin]

This PR was merged into the repository. The changes were merged into the following branches:

• main: d69dcec
• 22.2.x: 63e45bc