Skip to content

Conversation

@leandrowilliam
Copy link
Contributor

@leandrowilliam leandrowilliam commented Jan 7, 2026

Closes

Closes #1464

Changes

This PR decouples component console logging from the local configuration flag, allowing component logs to be visible regardless of whether the registry serves components from local filesystem or remote storage.
cc: @kmcrawford @GinGatt

What Changed

  1. Added enableComponentConsoleOutput configuration option (src/types.ts)

    • New boolean config property independent of storage location
    • Defaults to false for backward compatibility
    • Documented with clear purpose
  2. Updated options sanitizer (src/registry/domain/options-sanitiser.ts)

    • Added default value handling for the new config option
  3. Updated component execution context (src/registry/routes/helpers/get-component.ts)

    • Changed from checking conf.local to conf.enableComponentConsoleOutput
    • Component console is now passed based on the new flag, not storage location
  4. Enabled by default in dev mode (src/cli/facade/dev.ts)

    • oc dev command sets enableComponentConsoleOutput: true
    • Local development experience unchanged

@leandrowilliam leandrowilliam force-pushed the issues/1464-logger-param branch from e965fe4 to 13ed32f Compare January 7, 2026 21:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Component console output is not visible when registry uses remote storage

1 participant