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

docs: What does LB4 Beta mean for existing LB 3.x users #603

Closed
dhmlau opened this issue Oct 2, 2017 · 4 comments
Closed

docs: What does LB4 Beta mean for existing LB 3.x users #603

dhmlau opened this issue Oct 2, 2017 · 4 comments
Assignees
Milestone

Comments

@dhmlau
Copy link
Member

dhmlau commented Oct 2, 2017

http://loopback.io/doc/en/lb4/Migration-guide.html

need to change the title, NOT "Migration Guide"
(we're not ready for migration)
LB3 juggler can still be used with LB4 app
middleware -> will need to use Sequence
connect to: #485

Acceptance criteria

Outline:

  • Mapping key concepts from LB 3.x to LB 4.x:

    • The Model in 3.x has three parts - data modeling, persistence, remoting/REST API. In LB 4.x, remoting is moved to controllers. Persistence is moving to repositories. Data modeling stays on its own.

    • Extensibility. LB 3.x - operation hooks, remoting hooks, middleware. In LB 4.x, we have Sequence & Sequence actions, Bindings/Dependency Injection. We are considering introducing hooks at Controller level. Operation hooks are still available via legacy juggler bridge.

    • Connectors - staying the same for now.

    • Component model. LB 3.x - very simple component model. LB 4.x - much more powerful.

    • Authentication. LB 3.x has built-in set of models and auth/auth implementation. LB 4.x is fully pluggable and extensible. There is no built-in auth functionality available as of Beta release.

  • What features are part of Beta and more importantly what's not.

  • What are our post-Beta plans

    • highlight few items from the roadmap page that are relevant to people upgrading from LB 3.x
    • point readers to the full roadmap

Keep it high level, link to existing content (e.g. Thinking in LoopBack) for more details.

Rename http://loopback.io/doc/en/lb4/Migration-guide.html to a more appropriate name, put the content in that new page via a pull request, so that others can review the content.

@bajtos
Copy link
Member

bajtos commented Oct 3, 2017

Rephrase the content from #485 and put it in docs. Set the expectations of LB3 users right, make it clear what is part of LB4 Beta release and what's missing.

@bajtos bajtos changed the title Migration doc for beta docs: What does LB4 Beta means for existing LB 3.x users Oct 3, 2017
@bajtos bajtos changed the title docs: What does LB4 Beta means for existing LB 3.x users docs: What does LB4 Beta mean for existing LB 3.x users Oct 3, 2017
@raymondfeng
Copy link
Contributor

raymondfeng commented Oct 3, 2017

@raymondfeng
Copy link
Contributor

@dhmlau
Copy link
Member Author

dhmlau commented Oct 31, 2017

Talked to @raymondfeng, this is completed. Closing it.

@dhmlau dhmlau closed this as completed Oct 31, 2017
@dhmlau dhmlau added this to the Sprint 48 milestone Oct 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants