-
Notifications
You must be signed in to change notification settings - Fork 477
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(cdk): Schematics
add root path option
#3274
Conversation
Pull request was closed ✔️All saved screenshots (for current PR) were deleted 🗑️ |
ed97328
to
dd8d9a6
Compare
BundleMonUnchanged files (5)
No change in files bundle size Unchanged groups (1)
Final result: ✅ View report in BundleMon website ➡️ |
Visit the preview URL for this PR (updated for commit dd8d9a6): https://taiga-ui--pr3274-schematic-root-t0hdde8r.web.app (expires Thu, 22 Dec 2022 14:20:01 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4b5ece1e114386f6a105425ef799091475b249eb |
Codecov ReportBase: 61.49% // Head: 61.47% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #3274 +/- ##
==========================================
- Coverage 61.49% 61.47% -0.03%
==========================================
Files 1532 1533 +1
Lines 18090 18096 +6
Branches 2523 2524 +1
==========================================
Hits 11124 11124
- Misses 6507 6512 +5
- Partials 459 460 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
It will work ok if the root folder is not a project root, right? I mean if it has no package.json/angular.json in that folder and somebody just wants to run migrations for a particular folder? |
yes, it should work for particular folder without *.json |
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?
Closes #
What is the new behavior?
Does this PR introduce a breaking change?