* feat(core): update recommended extensions for new workspaces
* feat(core): fix vscode extensions not being generated, add migrations for workspace and jest to add extensions
* feat(core): add e2e to check .vscode/extensions.jon
* chore(core): fix logic for handling angular builders
* chore(core): fix e2e
* chore(core): revert change for angular-console to be default for everyone
* feat(testing): add projects into jest config
* chore(testing): update unit tests and fix presets with spreading a default
* chore(testing): fix node e2e
* chore(testing): review comment changes
* fix(testing): require jest config to resolve it better during migration
* fix(testing): require with appRootPath
* chore(testing): remove uneeded exports and imports
* feat(testing): add util to update jest configs.
* feat(testing): place configurations in jest config file rather than just the builder
* feat(testing): create migration and unit tests
* feat(testing): fix jest template
* feat(testing): fix jest template to correct unit tests
* feat(testing): include globals.ts-jest for all non babel configs
* feat(testing): include globals.ts-jest for node e2e
* feat(testing): fix migration to run properly. Also check for angular tests using the setupfile rather than builder
* feat(testing): clean up jest config functions and fix errors with some migrations
* feat(testing): add new line to package.json
* feat(testing): update object check to actually check for undefined
* chore(testing): loop through all project targets as well as targets
* chore(testing): update migration to be 10.0.0-beta.2
* fix(testing): update maxWorkers jest builder option to support string type
Jest supports both number and string args for the maxWorkers option, per their latest docs. This
updates the options for the jest builder to support both number and string types. Also updates the
docs accordingly.
ISSUES CLOSED: #2871
* fix(testing): fix test expectation missing property
the --coverage option was not being used in the builder at all, so provided no change in behavior.
The --codeCoverage option should be used instead
ISSUES CLOSED: #2564
