You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rework the way how an HTTP server is setup and configured for LoopBack applications (RestServer instances) following the approach outlined in #1082.
IMPORTANT
The spike was based on an assumption that we will support different frameworks (Express, Koa, etc.). Based on the spike outcome, we decided to go forward with a single framework and use Express request/response types everywhere. As a result, most of the spike code needs to be simplified by removing generic type arguments etc.
Rework the way how an HTTP server is setup and configured for LoopBack applications (RestServer instances) following the approach outlined in #1082.
IMPORTANT
The spike was based on an assumption that we will support different frameworks (Express, Koa, etc.). Based on the spike outcome, we decided to go forward with a single framework and use Express request/response types everywhere. As a result, most of the spike code needs to be simplified by removing generic type arguments etc.
https://github.com/strongloop/loopback-next/blob/2bddc47ccda56a50c52a8a92facd87e3a3f4944d/packages/http-server/src/common.ts#L12-L48
https://github.com/strongloop/loopback-next/blob/2bddc47ccda56a50c52a8a92facd87e3a3f4944d/packages/http-server/src/common.ts#L116-L212
Acceptance criteria
@loopback/rest
should use this new module to start/stop the server- The module should support HTTP config onlyOut of scope
The following features are out of scope, but please keep them in mind when designing the new module.
The text was updated successfully, but these errors were encountered: