Skip to content

docs(docs-infra): fix typo and malformed markdown bullet in angular-developer skill #68709

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.

Sign up for GitHub

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

Open
0avi wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −3
Open

docs(docs-infra): fix typo and malformed markdown bullet in angular-developer skill #68709

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions skills/dev-skills/angular-developer/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ metadata:

## Creating New Projects

If no guidelines are provided by the user, here are same default rules to follow when creating a new Angular project:
If no guidelines are provided by the user, here are some default rules to follow when creating a new Angular project:

1. Use the latest stable version of Angular unless the user specifies otherwise.
2. Use Signals Forms for form management in new projects (available in Angular v21 and newer) [Find out more](references/signal-forms.md).
Expand Down Expand Up @@ -65,8 +65,8 @@ When managing state and data reactivity, use Angular Signals and consult the fol

In most cases for new apps, **prefer signal forms**. When making a forms decision, analyze the project and consider the following guidelines:

- if the application is using v21 or newer and this is a new form, **prefer signal forms**.
-For older applications or when working with existing forms, use the appropriate form type that matches the applications current form strategy.
- If the application is using v21 or newer and this is a new form, **prefer signal forms**.
- For older applications or when working with existing forms, use the appropriate form type that matches the applications current form strategy.

- **Signal Forms**: Use signals for form state management. Read [signal-forms.md](references/signal-forms.md)
- **Template-driven forms**: Use for simple forms. Read [template-driven-forms.md](references/template-driven-forms.md)
Expand Down
Loading