mirror of
https://github.com/status-im/react-navigation.git
synced 2025-02-25 01:28:16 +00:00
ef82f1b5ff
the problem I see with many bug reports in this repo is that people write a very vague description of what their problem is and expect to get some help. I tried to: 1 . emphasise how important it is to include a runnable reproduction 2 . cut down on some extra words at the beginning of the template so it's more to the point
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
## The issue list is reserved for bugs and feature requests, not for questions.
|
|
|
|
For usage questions, try to:
|
|
|
|
- [Read the docs](https://reactnavigation.org/)
|
|
- [Ask on the Reactiflux (#react-navigation)](https://discord.gg/reactiflux)
|
|
- [Look for / ask questions on StackOverflow](https://stackoverflow.com/questions/tagged/react-navigation)
|
|
- Search for your issue - it may have already been answered or even fixed in the development branch. However, if you find that an old, closed issue still persists in the latest version, you should open a new issue.
|
|
|
|
---
|
|
|
|
### Current Behavior
|
|
- _If describing a bug, tell us what happens. Please provide a repository with code and steps to reproduce the bug. **Not providing code that other people can run makes is significantly harder to fix your bug.** Provide a screenshot when possible_
|
|
- _If suggesting a change/improvement, explain the difference from current behavior_
|
|
|
|
### Expected Behavior
|
|
- _If you're describing a bug, tell us what should happen_
|
|
- _If you're suggesting a change/improvement, tell us how it should work_
|
|
|
|
### Your Environment
|
|
|
|
| software | version
|
|
| ---------------- | -------
|
|
| react-navigation |
|
|
| react-native |
|
|
| node |
|
|
| npm or yarn |
|