How can extensions contribute (Express) middleware #5423
Labels
Docs
Extensions
Migration
REST
Issues related to @loopback/rest package and REST transport in general
stale
The pull request #5118 introduced the concept of Middleware to LoopBack 4 applications and added a bridging layer allowing users to mount Express middleware in LoopBack 4 applications.
Let's update our documentation for extension developers to explain when and how to use this new feature.
Related:
Acceptance criteria
#5304 added a helper allowing applications to load artifacts from other LB4 applications, see
https://loopback.io/doc/en/lb4/Booting-an-Application.html#boot-an-application-using-component
This concept can be useful to extension authors too, let's update our documentation to explain that in more details.
Related:
Acceptance criteria
Add content explaining when and how to leverage the concept of Express middleware new LB4 extensions
For example, we can add a new page to Extending LoopBack or expand one of the existing pages
Add similar content for people migrating a LB3 extension to LB4, see Migrating components and extension. Don't repeat yourself, the migration guide should focus on aspects unique to extensions migrating from LB3 and refer to content created in the step above wherever possible & appropriate.
The text was updated successfully, but these errors were encountered: