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.
4.0 - custom store?
See original GitHub issueIt could be idea to not work with a “built-in” store but rather to provide an adapter that satisfies a certain interface, with functions like getHex, e.t.c
In our example - we have an already existing state for the hex that travels through network, and it is an unnecessary chore to keep converting back / forth - and we don’t wanna store our state on the honeycomb and have it manage that.
Would you consider detaching the state and allowing clients to provide it via adapters or something?
Issue Analytics
- State:
- Created a year ago
- Comments:6 (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
Yup, this works! An interface + a “blessed” way to do it would be exactly the answer.
🎉 This issue has been resolved in version 4.0.0-beta.1 🎉
The release is available on:
Your semantic-release bot 📦🚀