feat(@angular-devkit/schematics): add schematics to generate ai context files. #30763
Conversation
angular-robot
bot
added
detected: feature
JeanMeche
force-pushed
the
generate-ai-file
branch
from
b3aef30 to
736c88d
Compare
JeanMeche
force-pushed
the
generate-ai-file
branch
2 times, most recently
from
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.
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.
Let's handle that as a follow-up when we have a better picture what we need to sync (we might have multiple schematics).
JeanMeche
force-pushed
the
generate-ai-file
branch
from
288dcfd to
53d6719
Compare
JeanMeche
force-pushed
the
generate-ai-file
branch
from
53d6719 to
7fd0e75
Compare
JeanMeche
force-pushed
the
generate-ai-file
branch
from
7fd0e75 to
c94f532
Compare
dgp1130
added
action: review
JeanMeche
force-pushed
the
generate-ai-file
branch
2 times, most recently
from
3dc7023 to
5ae2b77
Compare
packages/schematics/angular/config/files/__rulesName__.template
Outdated
Show resolved
Hide resolved
| "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.
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.
There was a problem hiding this comment.
As mentionned by @alan-agius4 here, the prompt would show for the others options. Or do you have an alternative in mind ?
JeanMeche
force-pushed
the
generate-ai-file
branch
2 times, most recently
from
048a5d7 to
19858e9
Compare
| expect(files).toContain('/bar/.gemini/GEMINI.md'); | ||
| expect(tree.readContent('/bar/.gemini/GEMINI.md')).toMatch(/^You are an expert in TypeScript/); |
JeanMeche
force-pushed
the
generate-ai-file
branch
from
19858e9 to
a59bed2
Compare
JeanMeche
force-pushed
the
generate-ai-file
branch
from
a59bed2 to
75b1fee
Compare
| const configOptions: ConfigOptions = { | ||
| project: options.name, | ||
| type: ConfigType.Ai, | ||
| tool: options.aiConfig as unknown as AiTool, |
There was a problem hiding this comment.
I'm not sure why I couldn't get the enums to match. It works fine for the packageManager above for example. (Yes I also tried with removing "none" from the enum here in ng-new).
…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.
JeanMeche
force-pushed
the
generate-ai-file
branch
from
75b1fee to
bbe0c40
Compare
ng generate config aito prompt support tools.ng generate config ai --tool=geminito specify the tool.ng new --ai-config=gemini`Supported ai tools: gemini, claude, copilot, windsurf, cursor.