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(rest): update readme #1158

Merged
merged 1 commit into from
Mar 22, 2018
Merged

docs(rest): update readme #1158

merged 1 commit into from
Mar 22, 2018

Conversation

virkt25
Copy link
Contributor

@virkt25 virkt25 commented Mar 20, 2018

connected to #988

Checklist

  • npm test passes on your machine
  • New tests added or existing tests modified to cover all changes
  • Code conforms with the style guide
  • Related API Documentation was updated
  • Affected artifact templates in packages/cli were updated
  • Affected example projects in packages/example-* were updated

@virkt25 virkt25 self-assigned this Mar 20, 2018
@virkt25 virkt25 requested a review from a team March 20, 2018 19:50
@@ -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
Copy link
Member

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"? :)

Copy link
Contributor Author

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).

Copy link
Member

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. :)

Copy link
Contributor

@shimks shimks left a 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';
Copy link
Contributor

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

@@ -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
Copy link
Contributor

Choose a reason for hiding this comment

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

openapi

@shimks
Copy link
Contributor

shimks commented Mar 20, 2018

In regards to swagger stuff, maybe we should mention that the actual code that generates the swagger spec lives outside of rest and in openapi-v3 and that we only reexport the module from rest.


## Contributions

- [Guidelines](https://github.com/strongloop/loopback-next/wiki/Contributing#guidelines)
- [Guidelines](https://github.com/strongloop/loopback-next/blob/master/docs/DEVELOPING.md)
Copy link
Contributor

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.

@virkt25
Copy link
Contributor Author

virkt25 commented Mar 22, 2018

@slnode test please

@virkt25 virkt25 merged commit 667b30b into master Mar 22, 2018
@virkt25 virkt25 deleted the docs/rest branch March 22, 2018 19:32
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

Successfully merging this pull request may close these issues.

4 participants