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.
Make binding internals a private API
See original GitHub issueOur binding internals need a refactor, for a number of reasons (which I won’t get into here), but we probably won’t have chance to do this before 11.0, and so it will need to be done during the 11.0 timeframe.
The problem with that is that much of our binding internals are exposed as a public API meaning that we won’t be able to refactor it without breaking our API promises. For that reason I think we’ll need to make much of our binding internals a private API for 11.0, in particular the following classes:
InstancedBindingBindingExpressionExpressionObserverExpressionNodeand derived classes- The concrete implementations of
IPropertyAccessorPlugin - The concrete implementations of
IDataValidationPlugin - The concrete implementations of
IStreamPlugin
Issue Analytics
- State:
- Created 10 months ago
- Comments:23 (20 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
I use
InstancedBindingon some code, wouldn’t it be possible to mark it as obsolete for example?@grokys Yeah, that would be perfect!