[Discussion] Feature based architecture + Styled-Components about ignite-andross HOT 4 CLOSED

structure

It feels much better grouping like this. Especially as the project grows.

I’ve landed on a new project organization that I’m loving. I gave the team an early preview a month or so ago.

@leonskim and I are wrapping up a 2 month client project with this new structure now.

styling libraries

styled-components and those types of libs are pretty good. I’ve tried most of them. I’ve found that they are much more useful on the web than in react native.

I’ve found that the ...spread operator works great and you don’t have the mental overhead of another library. That’s my opinion, I can see the use in them though! (Especially with dynamic themes)

d.i.y. boilerplates

You should definitely do this. That’s one of core tenants of Ignite 2!

PS: I totally missed this issue as well, sorry. I read it but forgot to come back. I need to find a better system to keep up with github follow ups.

from ignite-andross.

@harrisrobin I'm very sorry about the slow response time here! Glad you're liking our boilerplate!

I really like co-locating things like you've done.

We're currently working on a new file structure experiment. @skellock is driving that experiment forward in his latest project. I think it has similar characteristics to what you're proposing, although we haven't done a retrospective on the project yet.

styled-components is very cool. Another question for @skellock.

from ignite-andross.

@skellock Just ran across this thread and was considering doing the same re-factor to a feature based approach. When you say "feels much better grouping like this" did you mean the original or the feature based architecture. If the latter, do you think you'll be releasing a general overview of the new project organization. Thanks for all the work you've done, ignite is amazing!

from ignite-andross.

Check out the latest boilerplate, Bowser. Thank you!

from ignite-andross.