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.
vm.refs[] => vm.refs() to allow objects as _ref?
See original GitHub issuei’ve decided to change vm.refs from an array to a getter function. app code updates should be trivial (unless you were iterating vm.refs): vm.refs[key] will become vm.refs(key).
this is necessary for future-proofing the lib and allowing the internal refs impl to be non-uniform. the change will pave the way for _ref as well as _key on nodes to be objects OR values, transparently backed by Map, Weakmap or Hash.
invoking vm.refs with multiple args should bring back an array of vnodes while invoking it with 0 args should bring back an object containing both the Map and the Hash where object and value refs are held respectively.
expect the change to drop in the next few days.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (6 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 I’m happy you went in this direction, the use case is a lot cleaner. 👍
fastclick has been removed. _ref namespacing has been implemented as it’s more valuable than the more limited object _refs