Consider adding an option to control AccessMember's automatic object creation
- Dominant language
- JavaScript
- Stars
- 110
- Forks
- 98
- PR merge metrics
- No merged PRs in 30d
Description
`AccessMember` [automatically creates an object](https://github.com/aurelia/binding/blob/0.10.2/src/ast.js#L189) when assigning a value to a property on an object that doesn't exist.
[Some people love this behavior](https://github.com/aurelia/binding/issues/129). [Other people don't like it](https://github.com/aurelia/binding/issues/204).
Maybe we can make the behavior configurable?
cc @EisenbergEffect, @danfma
Contributor guide
Research direction
Start by reading the AccessMember implementation in src/ast.js around line 189, then review issues #129 and #204 for the arguments about automatic object creation. Define what configurable behavior should mean and how the option would be exposed; done should make assignment behavior selectable without changing the preferred default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100