Repository files navigation

Develop production ready Angular application. This is a small attempt to help and contribute to the angular community. The guidelines suggested below are purely from my experience, you can implement your own as well.

• Project Details - Explain internals of application

This app works on all morden browsers.If something doesn't work, pleasefile an issue

• Node - Version used to build this application is [12.14.0]
• NPM - In build in node installer, Version 6.13.4
• Angular-Cli - Version 10.0.0

Either download or git clone the repository.

git clone git@github.com:vijaysherekar/angular-architecture-skeleton.gitcd angular-architecture-skeletonnpm installnpm start

Then openhttp://localhost:4200 to see your app. When you are ready deploy to production, create a minified bundle withnpm run build-production

Youdon’t need to install or configure tools like webpack or TS compiler.
They are preconfigured and hidden so that you can focus on the code.

clone a project, and you’re good to go.

Purpose of this project is to provide a template or reference to angular developers so that they can extend it as per their requirements.
Following practices has been implemented

• Folder Structure
• Component Inheritance
• Error Handling
• Logging
• Separation of Concerns
• HTTP Interceptors
• Dynamic Import

The component library and css framework used is

• Angular Material

Above mentioned practices explain in details

• The application is separated into three modules
  • Core
  • Feature
  • Shared

These three modules provides the separation of concerns the application

Core module provides the pre-requisites to run the application. It imported only in the app module and it contains following

1. Custom Error Handler
2. Guards which are feature module wise, it will guard for each feature
3. Logger This will have helper methods such as log, info and error. According to log level mentioned in environment file for each environment it will print the logs or send the log to server if required
4. HTTP Interceptors currently we have the auth and logging
5. common this has common services such as
   1. user Details
   2. Application Constants
   3. Common API
   4. Check Access Service will check the respective logged in user has the rights to access the modules or not. It also helps to check user has read and write access for the accessible module

The business requirements are divided into multiple modules. Each feature module has the following

1. Multiple components
2. Every component will have service, which will do all the business logic and refered in the corresponding component
3. Every module will have data service, which will calls the respective api (Specifically for falcor api to create request object)
4. Routing will have canActivate guard

This module will be referenced into all the feature modules. It has following items

1. Angular Material Module

Component Inheritance will help to achieve below objectives

• Inject services which are common for all components
• As mentioned above this application will help to achieve both module level and operation level access to user for the respective module as per the configuration
• Unsubscribing and nullfying the properties and variables of component

Error handling will help to log the errors effectively and if required application can report those to server

logLevel property present in environment file, will help to print logs on browser or report it to server if required

Explain this point in Folder Structure

Currently we have added auth and ensure http interceptors, we can also add new interceptor which will send sanitized data to server

This feature will help to prevent the dependancies directly inject into module chunks. In our application we have used it at two places

1. Lazy loading of modules
2. Importing of JSONWEBTOKEN module

• Dan Wahlin Pluralsight angular architecture course
• Angular.io HTTP Interceptors

• Navin Narshetty
• Pratibha Kunjir
• Puja Shahu