This repository was archived by the owner on Apr 12, 2024. It is now read-only.
feat($parse): Add support for ES6 object initializers #14407
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add support for computed property names
- Add support for short notation in properties definitions
Eg. The expressions `{x}` and `{[x + 'foo']: 1}` are now valid.
|
We need to check with the Angular 2 team that they are going to adopt these in their template expression syntax before landing this. |
lgalfaso
added a commit
that referenced
this pull request
Apr 18, 2016
- Add support for computed property names
- Add support for short notation in properties definitions
Eg. The expressions `{x}` and `{[x + 'foo']: 1}` are now valid.
Closes: #14407
|
Landed this into master and 1.5.x branch |
kindy
pushed a commit
to kindy/angular.js
that referenced
this pull request
Jan 24, 2017
Adding the missing watches for ES6 object property which added in angular#14407
kindy
added a commit
to kindy/angular.js
that referenced
this pull request
Jan 24, 2017
Adding the missing watches for ES6 object property which added in angular#14407
3 tasks
kindy
added a commit
to kindy/angular.js
that referenced
this pull request
Feb 4, 2017
Adding the missing watches for ES6 object property which added in angular#14407 (cherry picked from commit 4b8bbf8) (and also apply commit 7278762)
3 tasks
ellimist
pushed a commit
to ellimist/angular.js
that referenced
this pull request
Mar 15, 2017
Add the missing watches for ES6 object computed properties which were implemented in angular#14407. Closes angular#15678
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
feature
What is the current behavior? (You can also link to an open issue here)
ES6 object initializers are not supported in expressions
What is the new behavior (if this is a feature change)?
ES6 object initializers are supported in expressions
Eg Shorthand property definition
{x}. Computed properties{[x + 'foo']: 'bar'}Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements
Other information:
Eg. The expressions
{x}and{[x + 'foo']: 1}are now valid.