Why use file type over feature based architecture?

[crisfcodes]

I would like to know what considerations you had for choosing a file based instead featured based architecture.

[jamonholmgren]

@crisfcodes Good question!

We started with strictly file-based with the original Ignite.

With Ignite 2.0, we moved to a feature-based architecture. However, over the next couple years, we found that this got awkward in a few ways, and things didn't always fit "neatly" into domains or features. Of course, you have a common or shared folder, but it starts feeling a bit bloated at some point.

So with Ignite successive versions, we ended up iterating back closer to the file-based convention, but not totally. If a component, style, or other file only applies to one screen, we co-locate it there. So it's basically a hybrid approach (which they mention in that article you linked to).

Hope this helps!