99x / 99x/react-scaffolder

Proposals

Open
#62 2 comments 0 reactions 0 assignees View on GitHub
claimed
Dominant language
JavaScript
Stars
44
Forks
15
PR merge metrics
No merged PRs in 30d

Description

- [ ] Do not use "components" folder. Some projects can use other structure (for example: src/pages) Move that to the .reactclirc
- [ ] Rename "parent and child" to "Class" and "Function" or "Stateless" as in [react docs](https://reactjs.org/docs/components-and-props.html#function-and-class-components)
- [ ] Update exist templates and add new (for example use proposal class properties and redux)
- [ ] Better validation for prop names (not empty and not starts from space or number)
- [ ] Do not ask question "Add propTypes" if you set at .reactclirc that you always use propTypes

Contributor guide

Open the contributing guide

Research direction

Start by reading the existing .reactclirc handling and current templates in the react-scaffolder CLI. Review how component names, prop names, and propTypes choices are validated, then compare the requested terminology and React documentation. Done means the configuration, template updates, validation rules, and propTypes behavior cover every checklist item, with matching tests where the project provides them.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs, react
Domain
cli, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.