git-coco 0.62.0 → 0.62.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -61,7 +61,7 @@ import { pathToFileURL } from 'url';
61
61
  /**
62
62
  * Current build version from package.json
63
63
  */
64
- const BUILD_VERSION = "0.62.0";
64
+ const BUILD_VERSION = "0.62.1";
65
65
 
66
66
  const isInteractive = (config) => {
67
67
  return config?.mode === 'interactive' || !!config?.interactive;
@@ -45365,12 +45365,23 @@ function createLogArgvFromUiArgv(argv) {
45365
45365
  // starting state. `coco ui --no-all` opts back to
45366
45366
  // current-branch-only.
45367
45367
  //
45368
+ // `?? true` re-asserts that default for the synthetic-argv path:
45369
+ // bare `coco` routes through defaultRouteHandler → buildSyntheticArgv,
45370
+ // which bypasses yargs and so never applies the `default: true` from
45371
+ // ui/config.ts — leaving `argv.all` undefined (#1169). Without the
45372
+ // fallback the workstation booted in compact (`--first-parent
45373
+ // --no-merges`) mode: fewer commits, branches "ahead" of HEAD hidden,
45374
+ // and cursoring/checking-out a branch whose tip wasn't in the compact
45375
+ // window triggered an anchored-context append that looped the graph
45376
+ // back to the initial commit. Explicit `--no-all` (argv.all === false)
45377
+ // is preserved because `false ?? true === false`.
45378
+ //
45368
45379
  // Note: passing `--branch foo` does NOT automatically scope away
45369
45380
  // from --all. If the user wants strictly that branch, they pass
45370
45381
  // `coco ui --branch foo --no-all`. We considered the implicit
45371
45382
  // scope-narrowing but it surprises users who pass `--branch` as
45372
45383
  // a "highlight this branch in the all-refs view" hint.
45373
- all: argv.all,
45384
+ all: argv.all ?? true,
45374
45385
  branch: argv.branch,
45375
45386
  format: 'table',
45376
45387
  interactive: true,
@@ -50384,6 +50395,11 @@ async function probeIsGitRepo() {
50384
50395
  * `InitArgv`, `UiArgv`, `WorkspaceArgv`) so we can't just spread the
50385
50396
  * raw default argv — we have to project the shared fields and let
50386
50397
  * the handler fill in command-specific defaults.
50398
+ *
50399
+ * Exported for testing: this is the path bare `coco` takes to the
50400
+ * workstation, and it intentionally does NOT set `all` — yargs's
50401
+ * `default: true` for `coco ui` never runs here, so the ui→log argv
50402
+ * mapping has to re-assert that default (#1169).
50387
50403
  */
50388
50404
  function buildSyntheticArgv(argv) {
50389
50405
  return {
package/dist/index.js CHANGED
@@ -78,7 +78,7 @@ var readline__namespace = /*#__PURE__*/_interopNamespaceDefault(readline);
78
78
  /**
79
79
  * Current build version from package.json
80
80
  */
81
- const BUILD_VERSION = "0.62.0";
81
+ const BUILD_VERSION = "0.62.1";
82
82
 
83
83
  const isInteractive = (config) => {
84
84
  return config?.mode === 'interactive' || !!config?.interactive;
@@ -45382,12 +45382,23 @@ function createLogArgvFromUiArgv(argv) {
45382
45382
  // starting state. `coco ui --no-all` opts back to
45383
45383
  // current-branch-only.
45384
45384
  //
45385
+ // `?? true` re-asserts that default for the synthetic-argv path:
45386
+ // bare `coco` routes through defaultRouteHandler → buildSyntheticArgv,
45387
+ // which bypasses yargs and so never applies the `default: true` from
45388
+ // ui/config.ts — leaving `argv.all` undefined (#1169). Without the
45389
+ // fallback the workstation booted in compact (`--first-parent
45390
+ // --no-merges`) mode: fewer commits, branches "ahead" of HEAD hidden,
45391
+ // and cursoring/checking-out a branch whose tip wasn't in the compact
45392
+ // window triggered an anchored-context append that looped the graph
45393
+ // back to the initial commit. Explicit `--no-all` (argv.all === false)
45394
+ // is preserved because `false ?? true === false`.
45395
+ //
45385
45396
  // Note: passing `--branch foo` does NOT automatically scope away
45386
45397
  // from --all. If the user wants strictly that branch, they pass
45387
45398
  // `coco ui --branch foo --no-all`. We considered the implicit
45388
45399
  // scope-narrowing but it surprises users who pass `--branch` as
45389
45400
  // a "highlight this branch in the all-refs view" hint.
45390
- all: argv.all,
45401
+ all: argv.all ?? true,
45391
45402
  branch: argv.branch,
45392
45403
  format: 'table',
45393
45404
  interactive: true,
@@ -50401,6 +50412,11 @@ async function probeIsGitRepo() {
50401
50412
  * `InitArgv`, `UiArgv`, `WorkspaceArgv`) so we can't just spread the
50402
50413
  * raw default argv — we have to project the shared fields and let
50403
50414
  * the handler fill in command-specific defaults.
50415
+ *
50416
+ * Exported for testing: this is the path bare `coco` takes to the
50417
+ * workstation, and it intentionally does NOT set `all` — yargs's
50418
+ * `default: true` for `coco ui` never runs here, so the ui→log argv
50419
+ * mapping has to re-assert that default (#1169).
50404
50420
  */
50405
50421
  function buildSyntheticArgv(argv) {
50406
50422
  return {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "git-coco",
3
- "version": "0.62.0",
3
+ "version": "0.62.1",
4
4
  "description": "zero-effort git commits with coco.",
5
5
  "author": "gfargo <ghfargo@gmail.com>",
6
6
  "license": "MIT",