The browser frontend for Chipster, a platform for bioinformatics data analysis. An Angular single-page application that talks to the REST APIs in chipster-web-server.
Run npm start or ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.
Run ng build to build the project, or npm run build for a production build. The build artifacts will be stored in the dist/ directory.
Run npm test to execute the unit tests via Vitest. Use npm run test:watch to re-run them on file changes.
Run npm run test:e2e to execute the end-to-end tests via Playwright. They drive a real browser against a running dev environment, so start the Angular dev server and chipster-web-server first. Chromium comes from the dev container image, see PLAYWRIGHT_BROWSERS_PATH.
Run npm run prettier to check formatting and npm run prettier-write to fix it. Prettier covers TypeScript, HTML, LESS and CSS under src/ and e2e/, and .prettierignore excludes the vendored code in src/assets.
A pre-commit hook checks staged files and refuses the commit if any are unformatted. npm install activates it by pointing core.hooksPath at .githooks. Skip it for one commit with git commit --no-verify, or turn it off in your clone with git config --unset core.hooksPath.
Run npm run lint to check and npm run lint-fix to fix what ESLint can fix by itself. ng lint checks the same files through the Angular builder. The rules are in eslint.config.mjs, in the flat config format that ESLint 9 requires.
The config extends the recommended sets of ESLint, typescript-eslint, eslint-plugin-import and angular-eslint, and adds the rules listed at the end of the typescript block by hand. Those hand-listed ones come from eslint-config-airbnb-base, which the project used until ESLint 9: airbnb has not been updated since, supports neither ESLint 9 nor typescript-eslint 8, and ships no flat config. Only the airbnb rules that catch mistakes were kept, not the ones that only enforce a style, which Prettier handles anyway.
no-explicit-any and no-empty-object-type are warnings rather than errors. Neither was enforced before and the codebase has hundreds of both, so they stay visible without failing the lint until the types are written properly. import/no-cycle warns for the same reason: the session services import each other in 17 cycles, which work only because Angular's dependency injection resolves them lazily, and untangling them is a job of its own.
To get more help on the Angular CLI use ng help or go check out the Angular CLI README.