Repository navigation
Code formatting - #69
Merged
Merged
Conversation
Member
|
Let's just get ci green, before merging. Better to do it now than later. It looks like it is only a ts ignore. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tackling #67
Added biome as a code-formatter and formatted everything with it. The corresponding commit has been added to the git-blame-ignore-revs so that we don't lose the git-blame infos.
Created new
package.jsonscripts for formatting and linting. The goal should be to integrate them into the CI, but since get codebase is currently created a ton of linter-issues and we probably have to rework a lot anyway, I would argue this is more of a long-term-goal for now.I also removed package-lock.json from gitignore and added it to the project in order to have reproducible environments.