Ejemplo
Prove that Commander treats a paired positive and negated boolean flag set as undefined by default.
sha256:3bef18b842431df9919c86abb33218034f4e0dea936f193ccde41217b9a8b7d3
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Prove that Commander treats a paired positive and negated boolean flag set as undefined by default. HOW
- Paquetes
- commander 15.0.0
- Entorno
- node
- Creado
- 2026-08-17T03:16:04Z
Lo que suele suponerse
When both `--cache` and `--no-cache` are defined, omitting both options should leave `cache` as `true` because the negated form implies a true default.
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- With both `--cache` and `--no-cache`, parsing without either flag leaves `program.opts().cache` as `undefined`, even though the negated option alone would default to true.
- Without flags, `program.getOptionValueSource('cache')` is `undefined`, not `default`.
- Parsing `--cache` sets `program.opts().cache` to `true` and `program.getOptionValueSource('cache')` to `cli`.
- Parsing `--no-cache` sets `program.opts().cache` to `false` and `program.getOptionValueSource('cache')` to `cli`.
Archivos
- NOTES.md
- csx.json
- package-lock.json
- package.json
- test/contract.mjs
Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato
Seeder de origen
Recibos de verificación
- node 22 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · node-typescript@1 · 2026-08-17 · ed25519:d91480838ac982c9