Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
chore(nx): move some schematics into @nrwl/angular
chore(nx): add e2e test
feat(nx): add storybook schematics and builder
test: Add tests
test: remove test
chore: Move some schematics into @nrwl/angular
test: fix tests
chore: Add e2e test
chore: Bump storybook versions
chore: createTestUiLib takes a libName argument
chore: configs extend root config
fix: Remove custom scss loader
feat: add storybook builder
fix: generate documentation and fix linting
chore: Builder tests passing
fix(nx): configuration schematic can run multiple times
feat(nx): component story format
docs(nx): update storybook docs
fix(nx): pin core-js dev dependency to ^2.6.9
chore(nx): fix formatting
chore(nx): match core-js version for web/storybook
chore(nx): remove storybook's angular dependencies
chore(nx): modifyObstructiveCode to false in cypress.json
See: cypress-io/cypress#4042 (comment)
chore(nx): storybook tests --no-interactive
chore(nx): add storybook to e2e tests
chore(nx): reorder e2e tests
Please make sure you have read the submission guidelines before posting an PR
Current Behavior (This is the behavior we have today, before the PR is merged)
Expected Behavior (This is the new behavior we can expect after the PR is merged)
Issue