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

[Spike] - Use alternate front-end engine (replace RestServer) #795

Closed
kjdelisle opened this issue Dec 12, 2017 · 1 comment
Closed

[Spike] - Use alternate front-end engine (replace RestServer) #795

kjdelisle opened this issue Dec 12, 2017 · 1 comment
Labels

Comments

@kjdelisle
Copy link
Contributor

kjdelisle commented Dec 12, 2017

blocked by #753

DRAFT - Please re-groom

Story

Investigate what some of the tradeoffs would be in swapping out our RestServer for an alternate implementation using a technology like Express, Koa, Micro, etc.

Acceptance Criteria

  • Create a new server implementation using one of the above technologies
  • Create a new Router that leverages our openapi-spec package to generate routes using one of the routing libraries for the chosen framework (ex. if you selected koa, use koa-router to build the routes based on the existing api spec(s))

Questions to Answer

  • Can we recycle core logic from our spec library between frameworks if we rewrite our router to use /foo/:id instead of /foo/{id}?
  • What approach would a developer need to take to build a custom server for LoopBack that can still leverage our OpenAPI v3 libs?
@dhmlau
Copy link
Member

dhmlau commented Apr 10, 2018

Duplicate of #1071

@dhmlau dhmlau marked this as a duplicate of #1071 Apr 10, 2018
@dhmlau dhmlau closed this as completed Apr 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants