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.
Improve the documentation
See original GitHub issueThere are 5 parameters in the copilot() HOC function, but only overlay and animated are documented.
Can you explain how to use other parameters?
I use this library on Android device, and I follow the example to create the tour guide.
But I found if I don’t add androidStatusBarVisible: false into copliot(), the Modal will have some offset so that part of view will be cut.
In fact, the statusBar is visible on my screen, I don’t understand why I should pass androidStatusBarVisible as false.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (5 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
@jordenchang55 Thanks, I took your way as well. I’ll report if any further information is captured from our user.
Yes, it would be better if there is a brief note in README. IMHO, an user should be able to understand the usage of library by reading README rather than code.