Resolve "Add Pipeline configuration"

Closes #2 (closed)

changed milestone to %v0.1.0

added 4 commits

• efd37a02 - chore(package): Rename package to make sure its an api client
• 1117f3ee - feat(tooling): Add linting
• d598af7f - style(formatting): Fix formatting for vite conf
• 1cd78c8a - ci(pipeline): Initialize basic pipeline

Compare with previous version

added 1 commit

• cb2c5fa3 - ci(lint): install packages before lint

Compare with previous version

added 1 commit

• 6e37db65 - v0.1.0-rc1

Compare with previous version

marked this merge request as ready

We use standard in front. I think we can simply use https://github.com/standard/ts-standard instead of whole eslint.

I am wondering if it makes sense anyway. It seems like the generated client is not generating linted code and I doubt we want to fix it manually each time. 😞

I am configuring it right now. I am thinking if it is even good that we ship the generated file. We could generate it in the pipeline before tests and building for publishing. That way noone would even dare to touch it to fix some errors directly in the file.

But this way we can never manually fix something

do we even want to manually fix anything in a generated file?

we have schema.yml commited, here we can make the manual fixes.

added 1 commit

• 451326dd - Add standard eslint config

Compare with previous version

approved this merge request

added 1 commit

• 7eeedb55 - Update lint script

Compare with previous version

mentioned in commit f3b27bb7

merged