react-navigation / react-navigation/react-navigation.github.io
[Feature Request] Provide class-based document in v5
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 324
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
I'm working on project that use many class-based components with React Navigation v4.
I'm tring to upgrade to to v5 but see v5 document provide only functional-based component in document.
It's really hard to migrate from v4 to v5 with current functional-based document.
Please provide class-based documentation.
(I want to use pure v5 API without Compatibility layer)
Thank you.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing v5 documentation and its functional-component examples, then compare them with the v4 class-based usage described in the issue. Done means the v5 documentation includes equivalent class-based guidance and explains migration without relying on the Compatibility layer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react, react-native
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100