Multiple nested modules and routing in Angular

Question

I have a project structure similar to something like this:

app.module
–– dashboard.module
–– overview.module
–––– profile.module
–––––– favorites.module

What you see are four levels of feature modules. (Consider them to have also multiple components etc.)

What would be the best way of setting up routing for these modules?

I would set up a routing module for every module, like this: app-routing.module, dashboard-routing.module, overview-routing.module (...)

But is that considered as a good practice in Angular? If not, what should one do instead?

Have you checked this answer? stackoverflow.com/questions/47353218/… — VascoCC
– VascoCC, Commented Mar 7, 2019 at 9:30

Muhammad Abdullah Shafiq · Accepted Answer · 2019-03-07 08:09:43Z

1

Each module should have their own routing file so the concerns remain separate. Its a good practice and i think you should go with this approach.

For Example, an Authentication module should handle its own routing like: /login, /signup, /forgot-password etc.

answered Mar 7, 2019 at 8:09

Muhammad Abdullah Shafiq

8646 silver badges17 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

L. Heider Over a year ago

I agree on that so far.

Muhammad Abdullah Shafiq Over a year ago

@L.Heider Thanks :) could you please accept this answer?

Rohan Kumar · Accepted Answer · 2019-03-07 08:08:48Z

0

In my opinion, you should not create multiple modules for a single type of interface. In your case there is a single application and a single module app.module is enough for it.

Now the question is that the alternate approach for another modules ?

So you should create Components for Dashboard, Overview, Profile, Favourites and manage routes in single app-routing.module file.

One more thing which should keep in mind, if you have multiple user interface like admin, sub-admin, user, etc. then it would be easy to maintain modules for each interface, and can manage their routing separately.

answered Mar 7, 2019 at 8:08

Rohan Kumar

40.7k11 gold badges81 silver badges111 bronze badges

2 Comments

L. Heider Over a year ago

But what if I like to implement lazy loading?

Rohan Kumar Over a year ago

Yes in that case you must go with the Module structure.

Collectives™ on Stack Overflow

Multiple nested modules and routing in Angular

2 Answers 2

2 Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related