Sample
Demonstrate that assigning '0' as a shortcut in Symfony Console InputOption evaluates to '0' starting in 7.0.3, while it incorrectly evaluated to null in 7.0.2 and earlier.
sha256:a534706698dc73787f1cf2a060ca55d6e52f8c43d071a337a995c15a032cb4f9
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Demonstrate that assigning '0' as a shortcut in Symfony Console InputOption evaluates to '0' starting in 7.0.3, while it incorrectly evaluated to null in 7.0.2 and earlier. HOW
- Packages
- symfony/console 7.0.3
- Environment
- php
- Created
- 2026-08-17T02:35:29Z
Commonly assumed
Passing the string '0' as an InputOption shortcut parameter correctly assigns it as a valid flag alias like -0.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- new InputOption('foo', '0')->getShortcut() evaluates to the string '0', proving that zero-string shortcuts are preserved rather than incorrectly dropping them as empty values.
- if (new InputOption('foo', '0')->getShortcut() !== '0') throw new Exception('Shortcut was incorrectly dropped as empty');
Files
- NOTES.md
- composer.json
- composer.lock
- csx.json
- test/contract.php
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- php 8 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · composer@1 · 2026-08-17 · ed25519:d91480838ac982c9