Skip to content

fix(@angular/cli): add schema versioning and metadata to example database#31757

Merged
clydin merged 1 commit intoangular:mainfrom
clydin:mcp/example-db-metadata
Nov 11, 2025
Merged

fix(@angular/cli): add schema versioning and metadata to example database#31757
clydin merged 1 commit intoangular:mainfrom
clydin:mcp/example-db-metadata

Conversation

@clydin
Copy link
Member

@clydin clydin commented Nov 11, 2025

This commit introduces schema versioning and metadata to the Angular CLI's example database.

A new metadata table has been added to both the runtime and build-time example databases. This table stores key-value pairs, initially including schema_version and created_at.

The find_examples tool now validates the schema_version of the loaded database. If a schema mismatch is detected, the tool throws a descriptive error message that guides the user on how to resolve the incompatibility (e.g., by updating their CLI or project's @angular/core package).

This change improves the robustness and maintainability of the example database by:

  • Ensuring compatibility between the CLI and the example database schema.
  • Providing actionable feedback to users when schema versions are incompatible.
  • Laying the groundwork for future metadata additions and database evolution.

…base

This commit introduces schema versioning and metadata to the Angular CLI's example database.

A new `metadata` table has been added to both the runtime and build-time example databases. This table stores key-value pairs, initially including `schema_version` and `created_at`.

The `find_examples` tool now validates the `schema_version` of the loaded database. If a schema mismatch is detected, the tool throws a descriptive error message that guides the user on how to resolve the incompatibility (e.g., by updating their CLI or project's `@angular/core` package).

This change improves the robustness and maintainability of the example database by:
- Ensuring compatibility between the CLI and the example database schema.
- Providing actionable feedback to users when schema versions are incompatible.
- Laying the groundwork for future metadata additions and database evolution.
@clydin clydin added the target: rc This PR is targeted for the next release-candidate label Nov 11, 2025
@clydin clydin requested a review from alan-agius4 November 11, 2025 17:25
@clydin clydin added the action: review The PR is still awaiting reviews from at least one requested reviewer label Nov 11, 2025
@alan-agius4 alan-agius4 added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Nov 11, 2025
@clydin clydin merged commit a9acc2e into angular:main Nov 11, 2025
35 checks passed
@clydin
Copy link
Member Author

clydin commented Nov 11, 2025

This PR was merged into the repository. The changes were merged into the following branches:

@clydin clydin deleted the mcp/example-db-metadata branch November 11, 2025 18:41
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Dec 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: @angular/cli target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants