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.

Sign up for GitHub

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

Jump to bottom

Make the factory HTTP framework function configurable #1290

Closed
hacksparrow opened this issue Apr 27, 2018 · 5 comments
Closed

Make the factory HTTP framework function configurable #1290

hacksparrow opened this issue Apr 27, 2018 · 5 comments
Assignees
@hacksparrow
Labels
REST Issues related to @loopback/rest package and REST transport in general stale

Comments

@hacksparrow
Copy link
Contributor

hacksparrow commented Apr 27, 2018 •
edited
Loading

Description / Steps to reproduce / Feature proposal

Make the factory HTTP framework function (express()) configurable and switchable with other Express-compatible frameworks

Current Behavior

None

Expected Behavior

#1255 (comment)

Acceptance Criteria

LB4 should accept an options object to configure the underlying HTTP framework.

See Reporting Issues for more tips on writing good issues
@hacksparrow hacksparrow self-assigned this Apr 27, 2018
@dhmlau dhmlau added the DP3 label Apr 27, 2018
@hacksparrow hacksparrow mentioned this issue May 3, 2018
Closed
@shimks
Copy link
Contributor

shimks commented May 3, 2018

Rejecting as the acceptance criteria is not clear enough. What is the 'options object'?

@shimks
Copy link
Contributor

shimks commented May 3, 2018

Dropping from dp3 from our agreed consensus in our estimation meeting

@shimks shimks added Core-GA and removed DP3 labels May 3, 2018
This was referenced May 7, 2018
Closed
Closed
@bajtos bajtos added the REST Issues related to @loopback/rest package and REST transport in general label May 16, 2018
@bajtos bajtos mentioned this issue May 16, 2018
Closed
@bajtos bajtos added post-GA and removed LB4 GA labels Jul 30, 2018
@bajtos
Copy link
Member

bajtos commented Jul 30, 2018

Removed from 4.0 GA scope, added to [EPIC] REST layer improvements (post-GA) #1452

@dhmlau dhmlau removed the non-DP3 label Aug 23, 2018
@dhmlau dhmlau removed the post-GA label Nov 2, 2018
@stale
Copy link

stale bot commented Oct 28, 2019

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Oct 28, 2019
@stale
Copy link

stale bot commented Nov 27, 2019

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hacksparrow hacksparrow

Labels
REST Issues related to @loopback/rest package and REST transport in general stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@hacksparrow @bajtos @shimks @dhmlau