Guide
Essentials
- Installation
- Introduction
- Context
- Payloads
Command Line
- CLI
- Initialize
- Generate
Directory Structure
- Tree
- Authentication
- Authorization
- Context
- Handlers
- Internal
- Middleware
- Models
Design File
- design.json
Models
- Models
Concerns
- Concerns
Examples
- TODO's
Meta
- Meet the Team
Concerns
Most api’s need to perform a few basic functions in order to answer a user’s request. These basic functions can most typically be broken down into three categories:
- Authentication i.e. “who are you?”
- Authorization i.e. “are you allowed to perform this action?”
- Business logic i.e. the action the user has requested to do
Many bugs can be introduced when these needs are intermingled, addressed out of order or not addressed at all. For this reason, design-first has separated these functionalities so they can be performed individually. However, sometimes information needs to be shared between each. For this reason, design-first implements route scoped context which can be used to pass information or callbacks.
The order that each route is processed is authentication, then authorization and finally business logic.
Caught a mistake or want to contribute to the documentation?
Edit this page on GitHub!