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: remove broken links #2282

Merged
merged 1 commit into from
Jan 24, 2019
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
38 changes: 12 additions & 26 deletions docs/site/FAQ.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,36 +17,22 @@ summary: LoopBack 4 is a completely new framework, also known as LoopBack-Next.

See [Crafting LoopBack 4](Crafting-LoopBack-4.md) for more details.

### What’s the timeline for LoopBack 4?

See
[Upcoming releases](https://github.com/strongloop/loopback-next/wiki/Upcoming-Releases).

### Where are the tutorials?

See [Examples and tutorials](Examples-and-tutorials.md).

### What features are planned ?

- 100% promise-based APIs and async and await as first-class keywords.
- Being able to choose to use JavaScript or TypeScript.
- Better extensibility, ability to override any aspect of the framework (for
example, no more built-in User - model pain, easily replace parts of ACL with
your own).
- Define APIs / remote methods with OpenAPI (Swagger).
- Organize business and other logic into controllers with their own opinionated
API or generate an PersistedModel style API.
- Better routing performance
- React SDK
- Create GraphQL based APIs
- GraphQL => juggler integration
- Advanced declarative caching support
- New DSL for defining APIs / Models
- Completely new tooling w/ Visual Studio Code integration
- More at
[Feature proposals](https://github.com/strongloop/loopback-next/wiki/Feature-proposals)

Add your feature requests at
### What features are planned?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we split this section in two parts - what has been done and what is being planned? We can also point readers to "LB3 Feature Parity" issue.

Copy link
Member Author

@dhmlau dhmlau Jan 24, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, I was thinking whether it's better to remove this list completely because features in plan are dynamic and changes over time. Maybe it's better to put something like:

Our roadmap is captured in <link to github search with "roadmap" label>.  
You can also check out our monthly milestone plans: https://github.com/strongloop/loopback-next/labels/Monthly%20Milestone.  

For LoopBack 3 users, here is the list of LB3 Feature parity we plan to implement in the future: https://github.com/strongloop/loopback-next/issues/1920.

What do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your proposal looks good 👍


Our roadmap is captured in
[here](https://github.com/strongloop/loopback-next/labels/roadmap). You can also
check out our
[monthly milestone plans](https://github.com/strongloop/loopback-next/labels/Monthly%20Milestone).

For LoopBack 3 users, here is the list of LB3 feature parity we wish to be
implemented in the future:
https://github.com/strongloop/loopback-next/issues/1920.

Do you have some other features in mind? Add your feature requests at
[loopback-next/issues/new](https://github.com/strongloop/loopback-next/issues/new).

### Why TypeScript?
Expand Down
7 changes: 0 additions & 7 deletions docs/site/LoopBack-3.x.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,10 +110,3 @@ Some of the highlights of LoopBack 4 include:
- Services: interact with existing REST APIs, SOAP Web Services, and other
forms of services/microservices
- Refactor the ORM into separate modules for different concerns

## Tentative roadmap

> Disclaimer: The release plan is tentative and it's subject to changes as the
> core team and community contributors make progress incrementally.

- [Upcoming releases](https://github.com/strongloop/loopback-next/wiki/Upcoming-Releases)
4 changes: 0 additions & 4 deletions docs/site/Preparing-the-API-for-consumption.shelved.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,6 @@ sidebar: lb4_sidebar
permalink: /doc/en/lb4/Preparing-the-API-for-consumption.html
---

{% include previous.html content=" This article continues
from [Implementing features](./Implementing-features.md).
" %}

## Preparing your API for consumption

### Interacting with your API
Expand Down