-
Notifications
You must be signed in to change notification settings - Fork 90
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
feat: create a conditional module #1409
feat: create a conditional module #1409
Conversation
8c1a92a
to
0d508f8
Compare
With the new `ConditionalModule` devs can now register modules based on keys in the `process.env` or have them registered as blanks modules under the guise of a dyanmic module. This works for nested modules, multiple imports, and dynamic modules. Signed-off-by: Jay McDoniel <jmcdo29@gmail.com>
0d508f8
to
d98a5f8
Compare
Just a question and also a curiosity this ConditionalModule module is a Public Api, right? |
Ok, seeing the last commit I'd say yes, it's a Public Api 😉👍 |
@jmcdo29 As soon as you find some time, can you create a PR to document this part in the documentation ? 🙌 🙂 |
@Tony133 that was the plan, just wanted to make sure this was feature complete before doing so, less updating back and forth to have to do |
LGTM Let me know if there's anything you want to add/if it's ready to be merged 🚀 |
|
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
There's no utility method for conditionally registering modules
Issue Number: #1407
What is the new behavior?
With the new
ConditionalModule
devs can now register modules based on keys in theprocess.env
or have them registered as blanks modules under the guise of a dynamic module. This works for nested modules, multiple imports, and dynamic modules.Does this PR introduce a breaking change?
Other information