-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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(rest): update readme #1158
Conversation
packages/rest/README.md
Outdated
@@ -12,18 +12,17 @@ with: | |||
- new custom routing engine (special thanks to @bajtos)! | |||
- tools for defining your application routes | |||
- OpenAPI 2.0 spec (`swagger.json`/`swagger.yaml`) generation | |||
- a default sequence implementation to manage the request and response lifecycle | |||
- a default sequence implementation to manage the request and response life cycle |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's wrong with "lifecycle"? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently life cycle
is the more correct usage / grammar as per online dictionaries and a VSCode extension I installed. That said, I can revert this change (I prefer lifecycle
as well).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Go with whatever you think that's correct.
i originally thought (coming from my son's learning material) life cycle
is more like some biological cycle that living things go through. But i'm no english expert. :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
swagger -> openapi
``` | ||
|
||
## Basic Use | ||
Here's a basic "Hello World" application using `@loopback/core` and | ||
`@loopback/rest`: | ||
Here's a basic "Hello World" application using `@loopback/rest`: | ||
|
||
```ts | ||
import {RestApplication, RestServer} from '@loopback/rest'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
super minor nitpick: extract out rest.getSync('rest.port')
since that's what we do in the CLI generated template
packages/rest/README.md
Outdated
@@ -12,18 +12,17 @@ with: | |||
- new custom routing engine (special thanks to @bajtos)! | |||
- tools for defining your application routes | |||
- OpenAPI 2.0 spec (`swagger.json`/`swagger.yaml`) generation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
openapi
In regards to swagger stuff, maybe we should mention that the actual code that generates the swagger spec lives outside of rest and in |
packages/rest/README.md
Outdated
|
||
## Contributions | ||
|
||
- [Guidelines](https://github.com/strongloop/loopback-next/wiki/Contributing#guidelines) | ||
- [Guidelines](https://github.com/strongloop/loopback-next/blob/master/docs/DEVELOPING.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it'd be better to link to https://github.com/strongloop/loopback-next/blob/master/docs/CONTRIBUTING.md which serves as the overall guideline and points to our DEVELOPING
doc as needed.
@slnode test please |
connected to #988
connected to #988
Checklist
npm test
passes on your machinepackages/cli
were updatedpackages/example-*
were updated