Frontend for CSCs Sensitive Data Archive metadata submitter. See backend for more info
Requirements:
Install backend from backend repository.
Install and run frontend either with:
docker-compose --env-file .env.example up --build
(add -d
flag to run container in the background).
docker-compose.yml
if you want to use some other setup;.env.example
if there are other parameters that need to be set up.pnpm install
followed with pnpm start
.
pnpm install
leaves corrupted package-lock.json, try to fix with pnpm install --frozen-lockfile
After installing and running, frontend can be found from http://localhost:3000
.
Run Vitest- and React Testing Library-based tests with pnpm test
. Check code formatting, TypeScript types and style errors with pnpm run lint:check
and fix them with pnpm run lint
. Respectively for formatting errors in json/yaml/css/md -files, use pnpm run format:check
or pnpm run format
.
.env.example
to your .env
file, these variables are needed to run some of the tests. cp .env.example .env
pnpm dlx playwright install --with-deps
OR if you have issue with your PATH
pnpm exec playwright install --with-deps
pnpm test:e2e
OR you can run the tests in UI mode:
pnpm test:e2e:ui
Note
e2e tests running in UI mode could have different result from the CLI. So if you are running the tests in UI mode, it may worth checking how they run in CLI as well, since the tests in Gitlab will be running in CLI.
We're following recommended settings from eslint, react and prettier -packages with couple exceptions, which you can find in .eslintrc
and .prettierrc
. Linting, formatting and testing are also configured for you as a git pre-commit, which is recommended to use to avoid fails on CI pipeline.
Running pnpm run build
builds the app for production to the build
folder.
See architecture.
Metadata submission interface is released under MIT
, see LICENSE.
If you want to contribute to a project and make it better, your help is very welcome. For more info about how to contribute, see CONTRIBUTING.