Skip to content

Support per-workspace validation exclusions#38

Closed
preco21 wants to merge 8 commits intotoss:mainfrom
preco21:feat/add-per-workspace-validation
Closed

Support per-workspace validation exclusions#38
preco21 wants to merge 8 commits intotoss:mainfrom
preco21:feat/add-per-workspace-validation

Conversation

@preco21
Copy link
Copy Markdown

@preco21 preco21 commented Dec 14, 2025

Summary

This changes introduce a new option, noValidationWorkspaces.

noValidationWorkspaces allows specific workspaces to bypass validation (usage checks) without disabling the catalog processing itself (via includedWorkspaces, ignoredWorkspaces).

Note: While the validation option can be used to disable validation, it only applies at the catalog-track level or globally, and cannot be scoped to individual workspaces.

Plus, corrected outdated JSON schema for validation option.

Motivation

In some cases, such as demo and playground — you may want catalogs to resolve normally while opting out of strict validation rules. This option enables that behavior in explicit way.

Example

# catalogs.yml
options:
  validation: strict
  includedWorkspaces: [apps-*]
  noValidationWorkspaces: [apps-demo]

list:
  stable:
    react: npm:18.0.0

Behavior

  • apps-demo skips all validation checks, even when validation is set to strict.
  • Catalog resolution and protocol handling remain fully functional in apps-demo.
  • All other apps-* workspaces continue to follow strict validation rules.

This keeps validation strict by default while allowing controlled, workspace-level exceptions.

@raon0211 raon0211 closed this Dec 19, 2025
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.

2 participants