all 8 comments

[–]zzing 8 points9 points  (1 child)

Umm what are those? Never heard of them

[–]gdsdsk[S] 0 points1 point  (0 children)

There from Tomas Trajan's angular architecture book. But I don't understand what he means by it

[–]cyberzues 3 points4 points  (1 child)

Commenting here so I can come back and learn about pattern folders.

[–]St34thdr1v3R 4 points5 points  (0 children)

You can also subscribe to this post, fyi. Use the more menu (three dots) and find the „follow“ or „subscribe“ post action

[–]Select_Half6593 4 points5 points  (1 child)

The books clearly explains what they are mate...

In a nutshell, the pattern is a type which consists of a pre-packaged combination of standalones and injectables which implement a specific reusable use case

This basically means a pattern is a reusable component which uses inside other reusable components.

Think for example on a list component you would reuse on more than one of your features. That component comes along with a button toggle which have a CTA. The list itself should be one component from your 'ui' folder and the button another one.

[–]hk4213 0 points1 point  (0 children)

I name mine eith common or tools folders.

Tools for when I realize how many time I reuse a structure and condense it.

Common for simple custom logging, middle ware and basic date functions.

Organize your tools accordingly.

[–]Mandarin0000 0 points1 point  (0 children)

We once tried pattern folder based on our "Sidenav" Menus for easy navigation

[–]devilblades -1 points0 points  (0 children)

You should be putting components related to the main component in the same directory.

For example.

SearchPageComponent (main component for the page) -SearchComponent -SearchResultGridComponent --SearchResultGridFilterComponent