Skip to content

Latest commit

 

History

History
40 lines (31 loc) · 2.05 KB

File metadata and controls

40 lines (31 loc) · 2.05 KB

Contribution Guides

  1. Get Set up
  2. Test Your Changes
  3. Write Unit Tests
  4. Submit a PR
  5. Publish Your Changes

1. Get Set up

To start contributing to this sample and get all set up, please refer to our local deployment guide.

Once you are locally all set up, create a new branch from main branch and start making your changes. Have fun!

Here is a quick overview of the repo code structure:

.
├── deploy - folder gathering all that is needed for Azure deployment
├── src
│    ├── controllers - folder gathering each controller which describes the path of each route │and the method to call.
│    ├── routes - folder gathering all the application's subpaths.
│    ├── services - folder gathering all services used in the project like Microsoft Graph, │Communication Services and Azure Active Directory.
│    ├── types - folder gathering any self-defined types.
│    ├── utils - folder gathering any helper functions.
│    ├── app.ts - file containing Express configurations and application configurations like │global paths and error handling.
│    ├── appSettings.ts - file containing all application settings about Graph Extensions, Communication Services and Azure Active Directory.
│    └── server.ts - file containing process of starting the Express server.
└── tests - folder gathering all unit tests.
     ├── controllers - folder gathering unit tests for each controller.
     ├── services - folder gathering unit tests for each service.
     └── utils - folder gathering all common mock data or testing methods.

Code dependencies: Azure Communication Services Authentication Server Sample - Code Dependency Diagram