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
Feature parity with LoopBack 3.x (and the lack of it) #1920
This epic is keeping a track of features that are available in LoopBack 3.x but don't have an easy-to-use alternative in LoopBack 4.x.
See also a loosely related Migration from LoopBack 3.x
referenced this issue
Nov 13, 2018
Hi everyone, we've identified the feature parity gap as listed above and created separate issues in
How it works
What if my wishlist is not on this list?
Create a new issue in this repo and put a comment in this issue.
How do I see which ones are popular requests from the community?
If everything goes right, we should be able to see it from this query: https://github.com/strongloop/loopback-next/issues?q=is%3Aopen+label%3A%22feature+parity%22+sort%3Areactions-%2B1-desc
Some of the big hitters here that are blocking us from migrating from LB3 to LB4 would be:
Hope this helps. I'm happy to go into any further detail. The above certainly isn't our full list, but these are the big ones that would keep us from migrating. A lot of the other items we've identified as gaps we could work around while the LB team adds the features.