Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
[Spike] Drop LB3 model files into LB4 app #2224
The migration approaches described in #485 and #1849 have a major problem: they require developers to migrate everything in one big change, there is no way how to migrate in smaller self-contained steps. I would like to look into ways how to make the migration more incremental.
Essentially, LB3 consists of three parts:
Carry over LB3 models (
The envisioned user experience
Things we will need to implement (or copy from LB3):
Things to implement anew:
Things that will not work (in the first version)
This was referenced
Jan 10, 2019
work in progress: https://github.com/strongloop/loopback-next/tree/spike/lb3
referenced this issue
Jan 22, 2019
Cross-posting #2274 (comment)
I have discussed the spike with @raymondfeng & @dhmlau and we agreed to stop pursuing this direction. While it does provide relatively easy migration path for LB3 users, there are too many downsides for us. Most importantly, we are re-introducing LB3 codebase that we wanted to get rid of, plus we are delaying the time when LB3 users will finally move to the new LB4 design.
For longer-term, we will look into ways how to simplify migration from LB3 models to LB4. I'll create follow-up spike stories for that soon.
The list of follow-up stories: