3 ms·
Nodded my head all through the article. Project setup hurts. "What folder do I put my components in? Even the ones that only get used on one page?" We need a D
by masonicb00m 11y ago
Nodded my head all through the article. Project setup hurts. "What folder do I put my components in? Even the ones that only get used on one page?"
We need a DHH.js to rise up and bring us "Rails, for React".
- lopatin 11y agoI put my components into app/components. This is the one, true directory structure. All other directory structures are wrong. \s
- Corrado 11y agoOpinionated programming was/is Rails' major contribution to the web world, as far as I'm concerned. By providing a baseline of things you need (directory structure, modules, logic flow, etc.) it made starting a project easy. In fact, it's just a single command. I think having all of these (ever changing) options is a sign of Javascripts immaturity; it's not bad, it's just growing pains. Hopefully someone will step up with a cookbook of best practices which will be respected and used throughout the community.