Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`banana-in-box` can be deprecated once new Angular compiler checks have auto-fixing
See original GitHub issueAccording to https://github.com/angular/angular/issues/42966, the compiler will start complain about wrong syntax in two-way binding, like we already do in banana-in-box rule.
In fact, the check has already been implemented in https://github.com/angular/angular/pull/42984 (https://github.com/angular/angular/commit/d6411c27291b69f46b3b7f648d3445c9c4ba3a4a) and https://github.com/angular/angular/pull/43232 (https://github.com/angular/angular/commit/fc85fa85ba7400b8a9b8a34677c6ada8ad301676).
So, with this in mind, should the banana-in-box rule be deprecated? cc @JamesHenry
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
FYI Joost from the Angular Team said that these compiler checks are still behind a flag so it’s not time to deprecate it yet
Cool, good catch! Yeah looks like we should mark this as deprecated in v13 onwards