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.
Rationale behind `data` path?
See original GitHub issueFrom the beginning this confused me a bit: For some reason, this library (and I think I also saw it in other libraries) gave special significance to the /data path, specifically by offering the dataToJS convenience helper function. From what I understand, the /data path has no special significance to Firebase per se, so, if I am not utterly wrong, this is based on some sort of convention, isn’t it?
Seeing how your library gives special attention to the /data path, references to documents which propose the convention of structuring your data in Firebase like this would be greatly appreciated, not sure if you or anyone else could provide those?
(Slightly off-topic: In general, any sort of list of resources and conventions that help new-comers better structure their data right from the start, would love to hear about it 😃 )
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 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
@Domiii can @tiberiuc close this ?
The /data that mentioned is related to the internal state of redux where the data is stored not to the path of firebase