feat: add kebab-case id field to project schema#17
Merged
Conversation
The project schema now includes an `id` field that is automatically generated as the kebab-case version of the project name. This allows project names to be human-readable strings while the id serves as a stable, filesystem-safe identifier used for directory naming. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Replace all uses of project `name` as the primary identifier with `id`. The `id` (kebab-case) is now used for directory paths, lookups, CLI output, and project resolution. The `name` field remains as a human-readable display name in the schema. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
@AmanAgarwal041 i think this requires your validation. let me konw as this made a lot of changes on the way the ID is used, now it's basically only using the ID instead of the name |
When loading a project.json that lacks an `id` field, the schema now automatically derives it as the kebab-case of `name`. This ensures existing projects created before the id field was introduced continue to work without manual migration. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Introduce a stable, filesystem-safe project id for projects and use it consistently across commands and APIs. Add an id field to ProjectConfig with a post-validator that derives a kebab-case id from the name when missing; update create to write and use project_config.id for directory names and messages. Make resolver return id instead of name, have get/download use id for target directories, and update get_project_path to resolve by id or fallback to config name for backward compatibility. Update output printing to display id, update sync to load and report project ids, and adjust/add tests to cover id generation, lookup, and behavior changes.
AmanAgarwal041
approved these changes
Apr 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The project schema now includes an
idfield that is automatically generated as the kebab-case version of the project name. This allows project names to be human-readable strings while the id serves as a stable, filesystem-safe identifier used for directory naming.Summary
Type of Change
SDK Affected
Testing
npm test/pytest)Checklist
Related Issues
Crafted by Transilience.ai