A typical LoopBack 4 app is composed of several elements:
- A controller to define the endpoints.
- A sequence to customize and contain the request-response process.
- Models for defining the data.
- A datasource to connect to database.
- A repository to link the model to the datasource.
- The application class which brings all of these together.
The application also supports the ability to create custom routes to define non-REST enpoints.
What was Achieved
Although it allows the creation of some simple apps, it is pretty limited and inflexible in what it can do.
Routes are limited to simple responses and has no access to the LoopBack request object, which contains a lot of additional information.
Controller methods are hard-coded in the helper library and leave no room for customization.
The personas we identified are:
Large scale application developer. Since large scale application are best developed with TypeScript, we concluded that this persona should be using the TypeScript version of LoopBack 4.
Extension developer. This persona wants to extend the capabilities of LoopBack 4 by writing custom extensions. Being technical enough, this persona should also be comfortable using TypeScript.
Call to Action
LoopBack’s future success depends on you. We appreciate your continuous support and engagement to make LoopBack even better and meaningful for your API creation experience. Please join us and help the project by:
- Reporting issues.
- Contributing code and documentation.
- Opening a pull request on one of our “good first issues”.
- Joining our user group.