mgechev / mgechev/angular2-style-guide

Style for *ngFor

Open
#44 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
1.2k
Forks
94
PR merge metrics
No merged PRs in 30d

Description

I saw several kinds of codes online, they are all working well, but I am not sure which style is recommended.

These are three of them:

```
*ngFor="#alert of alerts #i = index #l = last"
*ngFor="#alert of alerts; #i = index, #l = last"
*ngFor="#alert of alerts; #i = index; #l = last"
```

Maybe add one style guide for this? Thanks

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Review the repository's existing style-guide structure and the Angular-specific guidance around *ngFor, then document one recommended syntax and explain the alternatives if needed. Done means the guide clearly identifies the preferred style.

Written by the indexing model from the issue text.

Assessment

Tech stack
angular
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.