callstack / callstack/react-native-paper
Playground page for contributions
- Dominant language
- TypeScript
- Stars
- 14.5k
- Forks
- 2.2k
- Avg merge
- 5d 23h
- Merged PRs (30d)
- 12
Description
Would that be a good idea to add a playground page for anyone who needs to contribute and check particular component/set of components, so that contributors won't have to create that page each time by them selves or using example page with example components as a playground?
Benefits to add such a feature are:
1. Start working on the issue immediately instead of making appropriate circumstances in a file bloated with already existing useless code
2. Automatically git will ignore any changes in the playground, so you won't have to delete any code and make sure that you've wrote only clear code ( without useless comments of code and etc... )
3. Comfortable for contributors
Contributor guide
Research direction
Start by surveying the existing example page and the contribution workflow; the issue does not name specific files, tests, or entry points. Done would require an agreed playground page for testing components, with contributor changes excluded from normal code changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, react-native, typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100