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
This is a follow-up for the spike #2318, see the discussion and PoC code for more context.
Create an example app based on loopback-getting-started (@loopback/example-lb3app) to showcase LB3+LB4 integration. Add acceptance tests to verify few REST endpoints, also a test to verify that LB3 endpoints are included in the OpenAPI spec produced by the LB4 app.
Use use in-memory database instead of MySQL to avoid race conditions (PoC)
Add @loopback/booter-v3app to the project and configure it to load the legacy app
Write LB4-style acceptance tests for the REST API provided by the LB3 app. Cover the following REST API endpoints:
CoffeeShop.create
CoffeeShop.find
CoffeeShop.status
User.create
User.login
User.findById + provide a valid access token, expect 200
User.findById + provide a token of another user, expect authorization error
Add an acceptance test to verify the list of REST API endpoints contributed by the LB3 app. Make sure the test reports a useful error message on failure. Doing a deep-equal comparison of the entire OpenAPI spec IS NOT a good solution.
This is a follow-up for the spike #2318, see the discussion and PoC code for more context.
Create an example app based on loopback-getting-started (@loopback/example-lb3app) to showcase LB3+LB4 integration. Add acceptance tests to verify few REST endpoints, also a test to verify that LB3 endpoints are included in the OpenAPI spec produced by the LB4 app.
Related issues: #1849 #2389 #2391
Acceptance criteria
examples/lb3app
legacy
folder, make the following changes:debug
instead ofconsole.log
(PoC)@loopback/booter-v3app
to the project and configure it to load the legacy appCoffeeShop.create
CoffeeShop.find
CoffeeShop.status
User.create
User.login
User.findById
+ provide a valid access token, expect 200User.findById
+ provide a token of another user, expect authorization errorThe text was updated successfully, but these errors were encountered: