fix: restore schematics unit tests under Jest#570
Merged
Conversation
- Mock ora (ESM-only v9+) via moduleNameMapper so @angular-devkit/schematics/testing can be loaded in Jest's CJS environment - Add skipConsoleLogging utility and wrap all runSchematic calls to suppress NX warnings from polluting the test terminal - Fix updateTSConfig to only update the `files` field when it already exists (Angular 16+ uses include/exclude instead); add explanatory comments - Update issue-249 fixture to inject a `files` array alongside the Angular 10 comment, accurately simulating the scenario the test was written for - Add jest branch to createLogger with a comment explaining the fallback to console.warn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
filesfield when it already exists (Angular 16+ uses include/exclude instead); add explanatory commentsfilesarray alongside the Angular 10 comment, accurately simulating the scenario the test was written for