Spike: Migration guide from LB3 - General runtime #3718
Comments
9 tasks
12 tasks
This was referenced Oct 11, 2019
|
@bajtos , can we close this spike since you've created children issues? |
2 tasks
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Write an outline of a migration guide for LB3 users - an initial "seed" version that we can incrementally improve later.
Acceptance criteria
Collect a list of all different runtime artifacts & features we are aware of, use https://loopback.io/doc/en/lb4/Understanding-the-differences.html as the starting point. Few examples:
Update https://loopback.io/doc/en/lb4/Understanding-the-differences.html with any missing details, replace
TBDmarkers with real content. Add new table rows to capture missing features --> see docs: update "Understanding differences between LB3 and LB4" #3915Create a draft of the Migration guide in our docs, setup structure in the left navigation bar, etc. Create a placeholder section for each aspect/feature we need to document. --> see docs: add a skeleton of migration guide #3922
Describe how to import LB3 model into LB4 app (see Import LB3 model JSON file to LB4 model class #2480).
Show how to use
lb4 import-model.--> see docs: describe how to migrate model definition & built-in APIs #3969
If we know the instructions for migrating a certain aspect/feature, then write down the high level instructions as part of this spike.
For the remaining sections, create follow-up issues and reference them from the section text.
--> the task list:
While this story is a spike task, the skeleton of the migration guide should be landed and published in our docs. The spike aspect is related to the fact that we don't know the scope of the migration guide, which parts are easy to document and which will require further research.
Out of scope
User,AccessTokenandRole- see Spike: Migration guide from LB3 - Authentication & authorization #3719The text was updated successfully, but these errors were encountered: