Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(lb3-compat): Loopback3 compatibilty extension/package #4747

Closed
derdeka opened this issue Feb 26, 2020 · 3 comments
Closed

feat(lb3-compat): Loopback3 compatibilty extension/package #4747

derdeka opened this issue Feb 26, 2020 · 3 comments

Comments

@derdeka
Copy link
Contributor

derdeka commented Feb 26, 2020

Suggestion

I suggest to create a @loopback/lb3-compat package to reimplement the builtin lb3 models and behavior with lb4 components like interceptors etc.

Use Cases

To support lb3 migrations it might be helpful to rebuild the lb3 behavior and models in lb4 for a faster migration path for exisiting applications. It does not make sense that each user needs to do this by going through the docs.

This could be also helpful for importing lb3 models into lb4. Relates to #4737.

Acceptance criteria

TBD - will be filled by the team.

@dhmlau
Copy link
Member

dhmlau commented Mar 23, 2020

@derdeka, thanks for your suggestion. For the built-in LB3 models, do you mean User and ACL models? @jannyHou is creating a extension/component for JWT authentication, so whoever trying to use JWT authentication in LB doesn't need to follow the same steps. :). See #4903. Is that something you have in mind?

The benefit of having such extension is that it would benefit not only LB3 users who are migrating their application to LB4, but also someone who is building LB4 app from scratch.

@stale
Copy link

stale bot commented Dec 25, 2020

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Dec 25, 2020
@stale
Copy link

stale bot commented Jul 14, 2021

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Jul 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants