-
Notifications
You must be signed in to change notification settings - Fork 0
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: ask whether to add routing in ng-add
schematic
#975
feat: ask whether to add routing in ng-add
schematic
#975
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @davidlj95 and the rest of your teammates on |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #975 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 86 86
Lines 365 372 +7
Branches 52 54 +2
=========================================
+ Hits 365 372 +7 ☔ View full report in Codecov by Sentry. |
📦 Bundle size (Angular v16)Git ref:
|
📦 Bundle size (Angular v15)Git ref:
|
📦 Bundle size (Angular v18)Git ref:
|
📦 Bundle size (Angular v17)Git ref:
|
🎉 This PR is included in version 1.0.0-beta.27 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Issue or need
ng-add
schematic added in #962 just adds the core provider.It could be nice for users to add routing and many metadata modules too.
Proposed changes
Add an option to the
ng-add
schematic to enable the routing module.It can be enabled by
ng add @davidlj95/ngx-meta --routing
. Defaults to not enabled.It's disabled by default and doesn't ask the user via
x-prompt
in the schema yet.This way, we can start asking for both routing & metadata modules all at once. At that moment, docs may be updated to reflect this new feature.
Quick reminders