Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Signed-off-by: Rifa Achrinza [email protected]
Currently, LoopBack 4 does not provide full parity of the features from LoopBack 3. This PR is intended to add a warning for existing users of LoopBack 3 on the docs page (see: #1920 (comment)).
While there is a pinned issue to keep track of this, it may be hidden to the average user. Hence, this PR intends to put forward the pinned issue in more clearly.
This is to prevent users from taking extra time to work around the lack of feature parity that may not have been known to them due to lack of warning in the docs.
Checklist
👉 Read and sign the CLA (Contributor License Agreement) 👈
npm test
passes on your machine👉 Check out how to submit a PR 👈