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: add lb3 parity warnings #4466

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/site/Understanding-the-differences.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,8 @@ model definitions, migrating their application incrementally.

## Concept/feature mapping

{% include note.html content="See the [GitHub issue](https://github.com/strongloop/loopback-next/issues/1920) for a full list of features that have not been migrated to LoopBack 4." %}

In Loopback 3.x (and earlier), models were responsible for both accessing data
in other systems (databases, SOAP services, etc.) and providing the
application's external REST API. This made it easy to quickly build a REST
Expand Down
2 changes: 2 additions & 0 deletions docs/site/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,8 @@ multiple repos, as in v3. However, examples and externally-developed components
will be in separate repositories.
'%}

{% include important.html content="Certain features from LoopBack 3 may still be a work in progress or are not planned to be migrated to LoopBack 4. See [Understanding the differences](understanding-the-differences.md)." %}

LoopBack is a highly extensible, open-source Node.js and TypeScript framework
based on Express that enables you to quickly create APIs and microservices
composed from backend systems such as databases and SOAP or REST services.
Expand Down