Skip to content
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

ngFor with possibility of assign key value like ES6 feature #19333

Closed
titusfx opened this issue Sep 22, 2017 · 2 comments
Closed

ngFor with possibility of assign key value like ES6 feature #19333

titusfx opened this issue Sep 22, 2017 · 2 comments
Labels
area: common Issues related to APIs in the @angular/common package area: core Issues related to the framework runtime feature Issue that requests a new feature

Comments

@titusfx
Copy link

titusfx commented Sep 22, 2017

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ x ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

<tag *ngFor="let keyValue of getAMap() | myPipeToGetKeysAndValue" >

Right now getting key and value of a map, you need to create a pipe instead of having one builtin,

Expected behavior

<tag *ngFor="let [key, value] of getAMap() | builtInAngularPipeKeysValue" >

this is a feature of ES6

Minimal reproduction of the problem with instructions

What is the motivation / use case for changing the behavior?

Environment


Angular version: X.Y.Z


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

@IgorMinar IgorMinar added area: common Issues related to APIs in the @angular/common package area: core Issues related to the framework runtime labels Sep 22, 2017
@Toxicable
Copy link

Toxicable commented Sep 22, 2017

Duplicate of #2246 (comment)

@chuckjaz chuckjaz added the feature Issue that requests a new feature label Nov 1, 2017
@chuckjaz chuckjaz closed this as completed Nov 1, 2017
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: common Issues related to APIs in the @angular/common package area: core Issues related to the framework runtime feature Issue that requests a new feature
Projects
None yet
Development

No branches or pull requests

4 participants