mirror of
https://github.com/game-ci/unity-builder.git
synced 2026-09-29 12:07:05 -07:00
frostebite
96e259d13f
Real bug caught by live CI (not the release-timing gap, which was separately expected and has since resolved): "--flag value" as two argv tokens is ambiguous when value itself starts with "-" - e.g. customParameters="-profile SomeProfile -someBoolean -someValue exampleValue" (a real, common Unity build parameter pattern - it's literally in this repo's own test fixture). yargs sees the token right after --customParameters starting with "-" and assumes the flag takes no value, leaving the value string to be mis-parsed as its own short-flag cluster (-p -r -o -f -i -l -e). Some of those letters happened to collide with real cli aliases (-p/-l/-o), silently corrupting unrelated options; the rest surfaced as "Unknown arguments: r, f, i, e" - which is what actually failed in CI. Verified against the real cli binary locally (bun run src/index.ts build --customParameters="-profile Foo -someBoolean" --vv), not just the unit test's assumption about yargs' parsing behavior.