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.
Suggestion - Update Readme with more information
See original GitHub issueHi,
I’m interested in using this package, but I’m a little wary of implementing it since the readme is kind of light on details.
For instance, does this work with all android and ios devices with notches? What does this package actually do? (description of how it works) Will this be actively maintained? How does this handle devices without notches?
If you could add a bit more to the readme I think that would help people to decide on using this. It’s coming recommended from @mikehardy via react-native-device-info as a replacement for their hasNotch method, so maybe adding that could also help?
Issue Analytics
- State:
- Created 4 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
@janicduplessis this is spilling over from discussion on react-native-device-info
@rtman here is the previous thread: https://github.com/react-native-community/react-native-device-info/issues/594#issuecomment-527669853
It does not exist yet but we are thinking it is possible to expose it so then you can answer the boolean “hasNotch” question
Going to close this, if anyone (or myself when I get time) wants to add more details to the readme feel free to open a PR.