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

[Boot] Support advanced use cases for BootExecutionOptions #1021

Closed
virkt25 opened this issue Feb 21, 2018 · 2 comments
Closed

[Boot] Support advanced use cases for BootExecutionOptions #1021

virkt25 opened this issue Feb 21, 2018 · 2 comments

Comments

@virkt25
Copy link
Contributor

virkt25 commented Feb 21, 2018

@loopback/boot when used via BootMixin only provides support for BootOptions a.k.a. conventions. To support a variety of use cases such as generating OpenAPI Spec without starting a server, APIC use cases, etc, we need to provide support for BootExecOptions via the Mixin.

There is some ground work already done with BootExecOptions as part of the initial PR for boot however there needs to be more discussion and consensus around the API design of consuming BootExecOptions from a user perspective, and the options it should support.

The current ExecOptions provides support for binding additional Booters, filtering Booters that are executed during a call to boot and the phases that are executed. We should determine the exact nature of these filters and how they handle scenarios such as a Booter with a given name not being bound, a phase name that doesn't exist. Do we allow arbitrary phases to be created? How can this be leveraged by a Booter, etc.

Some related discussion can be found in the original PR: #858, #858 (comment), #858 (comment), #858 (review),

@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
Projects
None yet
Development

No branches or pull requests

3 participants