Solution structure

The solution structure corresponds to that of the Microsoft Graph API reference menu structure to aid findability between the two.

Each menu item on the left of the API Documentation page has its own separate folder in the 'MicrosoftGraphAPI' project in the Linx Solution.

So for example, functionality related to Users is grouped into its own folder like its title on the documentation page.

Solution
└── MicrosoftGraphAPI
    ├── Application
    └── Users

Each of these folders then contains separate folders for each of the sub-sections like on Microsoft Graph API reference page.

In the case of the 'Users' - the sub-sections 'Calendar' and 'Contacts', will each get their own folder in the 'Repos' folder in the Linx Solution.

Solution
└── MicrosoftGraphAPI
    ├── Applications
    |   └── Application
    └── Users
        ├── Calendar
        └── Contacts

Inside each of these folders then contains 2 sub-folders which are:

• Requests: Connector functions which execute a HTTP request and process the response.
• Types: Objects used for de-serializing the inputs and outputs of the functions.

For example. the 'create calendar' method, is nested under the 'Users - Calendar' section and therefore will take the below structure:

Solution
└── MicrosoftGraphAPI
    └── Users
        └── Calendar
            ├── Requests
            |   ├─ CreateCalendar 
            |   └─ CreateEvent
            └── Types
                ├─ Calendar 
                └─ CalendarOwner