Two-way bind @ syntax breaks one-way bind
- Dominant language
- ActionScript
- Stars
- 380
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
Perhaps two-way bind @ syntax (i.e. value="@{myprop}") is not supported yet, but it doesn't even work for one-way binding; it won't update at all when the source changes. (Broken in JS and SWF, works fine in Flex.)
See attached example.
[TestTwoWayBinding.mxml.txt](https://github.com/apache/royale-asjs/files/7448669/TestTwoWayBinding.mxml.txt)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading and running the attached TestTwoWayBinding.mxml.txt example in the JS and SWF targets, then trace how value="@{myprop}" is handled when the source changes. Done means the one-way binding updates in JS and SWF, while preserving the existing working Flex behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100