We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank you @quentinderoubaix for raising the points.
npm run test -w webapp
angular.json
npm run test:playwright
npm run test:playwright:sanity
.gitignore
@o3r/eslint-config-otter
@angular-eslint/eslint-plugin-template
The text was updated successfully, but these errors were encountered:
No recommendation of the pipeline. No doc / setup for dependency / source code scanning (npm/yarn audit, CodeQL etc.)
Is related to the feature #689 .
Sorry, something went wrong.
No branches or pull requests
Context
Thank you @quentinderoubaix for raising the points.
Proposal
npm run test -w webapp
fails)Tracked via [Bug]: tests not running on new otter webapp #1606
angular.json
still includes karma / jasmineWe won't remove the leftover references for karma/jasmine for two reasons
npm run test:playwright
ornpm run test:playwright:sanity
fail) Tracked via [Bug]: playwright tests not running on new otter webapp #1632.gitignore
does not include the folder test-results of playwrightTracked via [Bug]: playwright tests not running on new otter webapp #1632
For the CI/CD part: [Feature] Generate workspace with CI/CD capacity #689
@o3r/eslint-config-otter
as@angular-eslint/eslint-plugin-template
is not installedCould be related to [Bug]: Linter does not work on a new Otter webapp in a monorepo #1661
Tracked via [Bug]: lint errors on new Otter applications and libraries #1690
The text was updated successfully, but these errors were encountered: