-
Notifications
You must be signed in to change notification settings - Fork 11.9k
feat(@angular-devkit/schematics): add schematics to generate ai context files. #30763
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
b3aef30
to
736c88d
Compare
70ae7ec
to
288dcfd
Compare
throw new SchematicsException(`Project name "${options.project}" doesn't not exist.`); | ||
} | ||
|
||
// Keep this file in sync with the one presented here https://angular.dev/ai/develop-with-ai |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should do something automatted or document it on the FW side, since when there is a change there, a PR needs to be opened here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's handle that as a follow-up when we have a better picture what we need to sync (we might have multiple schematics).
288dcfd
to
53d6719
Compare
53d6719
to
7fd0e75
Compare
7fd0e75
to
c94f532
Compare
c94f532
to
3dc7023
Compare
…xt files. * `ng generate config ai` to prompt support tools. * `ng generate config ai --tool=gemini` to specify the tool. Supported ai tools: gemini, claude, copilot, windsurf, cursor.
3dc7023
to
5ae2b77
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This appears out of date. Please update with the content from https://github.com/angular/angular-cli/blob/main/packages/angular/cli/src/commands/mcp/instructions/best-practices.md
function addAiContextFile(options: ConfigOptions): Rule { | ||
const files: ContextFileInfo[] = []; | ||
|
||
const geminiFile: ContextFileInfo = { rulesName: 'GEMINI.md', directory: '.gemini' }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can these constants be moved to a module level constant object literal?
That would also remove the need for the switch and also allow for easier expansion/adjustment of tools.
"x-prompt": "Which type of configuration file would you like to create?", | ||
"$default": { | ||
"$source": "argv", | ||
"index": 0 | ||
} | ||
}, | ||
"tool": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be a multi-select prompt?
We could still default to having them all selected. Would need to change the type to a string array though. But it's probably unlikely that everyone would want all available tools when not specifying the option. Especially since the option may not be known to even exist.
ng generate config ai
to prompt support tools.ng generate config ai --tool=gemini
to specify the tool.Supported ai tools: gemini, claude, copilot, windsurf, cursor.