fix: honor non-interactive template defaults and Windows paths #71

2026-10-30T15:20:49Z

KofTwentyTwo commented

2026-10-30 15:20:49 +00:00

(Migrated from github.com)

Non-interactive qqq init ignored manifest defaults and could wait for input when a template was unknown. On Windows, backslashes escaped Velocity path placeholders, and parsing an HTTPS template URL as a filesystem path stopped template downloads.

Apply and validate manifest defaults with explicit overrides, return NOT_FOUND for unknown templates without prompting, normalize template separators before interpolation, and let invalid local-path probes continue through the supported Git URL validation. Interactive template fallback remains covered.

Validation at a779db2c517f293beb0fa93b5b0f2b99847758a5:

Four non-interactive regressions and one Windows path regression failed before their fixes. The real Windows native initialization failure reproduced the HTTPS colon error.
Gitea Mac ARM64 run138 and Windows AMD64 run140 each pass the full Maven lifecycle, native build, then235 tests across26 reports with zero failures/errors/skips. Downloaded artifacts were independently checked for source, checksums, native architecture and test totals.
Hosted unit/build and CodeQL checks pass. This branch contains only the native fixes on top of main.

This qualifies CLI builds and native behavior; it does not publish a release or claim signing/notarization or Intel macOS coverage.

Non-interactive `qqq init` ignored manifest defaults and could wait for input when a template was unknown. On Windows, backslashes escaped Velocity path placeholders, and parsing an HTTPS template URL as a filesystem path stopped template downloads. Apply and validate manifest defaults with explicit overrides, return NOT_FOUND for unknown templates without prompting, normalize template separators before interpolation, and let invalid local-path probes continue through the supported Git URL validation. Interactive template fallback remains covered. Validation at `a779db2c517f293beb0fa93b5b0f2b99847758a5`: - Four non-interactive regressions and one Windows path regression failed before their fixes. The real Windows native initialization failure reproduced the HTTPS colon error. - Gitea Mac ARM64 run138 and Windows AMD64 run140 each pass the full Maven lifecycle, native build, then235 tests across26 reports with zero failures/errors/skips. Downloaded artifacts were independently checked for source, checksums, native architecture and test totals. - Hosted unit/build and CodeQL checks pass. This branch contains only the native fixes on top of main. This qualifies CLI builds and native behavior; it does not publish a release or claim signing/notarization or Intel macOS coverage.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qctl#71