boilersuit
A super-powered generator for selectors, reducers, actions, constants and sagas in react-boilerplate
by mattpocockJavaScript
Meet the team
See all 1 on GitHub →
Commit activity
Last 12 weeks · 0 commits
Community health
1 of 6 standards met
28
✓README○License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 7 discussions · Last activity 7y ago
See all on GitHub →
This is crucial for when you want to import your own logic into the reducers. Rewriting the whole reducer each time is not good enough for how extensible we want reducers to be.
Currently, we are rather bound to the folder structure of , and its pattern of segmented containers. How would suit handle a plain redux environment? Where would the file go? Boilersuit thrives in regimented folder structures. Once we have an idea of a folder structure for a plain redux project, we can get started extending it.
It would be really cool to be able to specify Flow or Typescript in the suit up command, automagically generating and associating interfaces and types in the appropriate places. Something like .
Recent fixes
This means we need to change the logic of some of the search functions. Mostly an internal bug, but left here to remind me to work on it.
Suit requires explanation - a series of readme videos are incoming.
In other words, takes a suit with tens of reducers and turns it into a suits folder with many smaller suit files in it. This could be overkill on the automation front.
Structured data for AI agents
Repository: mattpocock/boilersuit. Description: A super-powered generator for selectors, reducers, actions, constants and sagas in react-boilerplate Stars: 31, Forks: 1. Primary language: JavaScript. Languages: JavaScript (100%). Open PRs: 0, open issues: 7. Last activity: 7y ago. Community health: 28%. Top contributors: mattpocock.