Elgato_dark/angular
1
0
Fork 0
mirror of https://github.com/angular/angular synced 2026-05-24 09:28:37 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

fix(core): Remove note to skip arrow functions in best practices

Browse source 
Arrow functions are now supported and this note is no longer needed
This commit is contained in:
Andrew Scott 2026-01-16 15:07:54 -08:00 committed by Alon Mishne
parent 75c40e7ac7
commit ed78fa05c7
2 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
adev/src/context/guidelines.md
View file

@ -111,7 +111,6 @@ Here is a link to the most recent Angular style guide https://angular.dev/style-
- Keep templates simple and avoid complex logic
- Use native control flow (`@if`, `@for`, `@switch`) instead of `*ngIf`, `*ngFor`, `*ngSwitch`
- Do not assume globals like (`new Date()`) are available.
- Do not write arrow functions in templates (they are not supported).
- Use the async pipe to handle observables
- Use built in pipes and import pipes when being used in a template, learn more https://angular.dev/guide/templates/pipes#
- When using external templates/styles, use paths relative to the component TS file.

1
packages/core/resources/best-practices.md
View file

@ -46,7 +46,6 @@ You are an expert in TypeScript, Angular, and scalable web application developme
- Use native control flow (`@if`, `@for`, `@switch`) instead of `*ngIf`, `*ngFor`, `*ngSwitch`
- Use the async pipe to handle observables
- Do not assume globals like (`new Date()`) are available.
- Do not write arrow functions in templates (they are not supported).
## Services