Skip to content

Restructure the Routing #27

Description

@KevinStarWars

The routing of the template does not follow the best practices. It is chaotic and does not have a clear structure. Additionally it does not use Lazy Loading, which it should as a template for enterprise software.
These tasks derive from the chaotic routing:

  • Structure the routing by feature areas
  • Use Lazy Loading in order to load feature areas and their features lazy
  • Use the RouterModule’s full capabilities and use canActivateChild in order to guard
  • Remove routes, which are configured multiple times

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions