Skip to content

Conversation

@pheyvaer
Copy link
Contributor

@pheyvaer pheyvaer commented Feb 8, 2024

I added linting to the repo. I added instructions for it in the README. I already automatically fixed some of the issues, but there are some left. Most of them are about the documentation, which is crucial for me to understand what is happening. If you are ok with how the linting is set up, can you then have a look at fixing the remaining issues? This should happen in a separate branch.


You run the linter via
```shell
npm run lint:ts
Copy link
Collaborator

@argahsuknesib argahsuknesib Feb 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

running this gives me an output as,

✖ 535 problems (101 errors, 434 warnings)
  0 errors and 2 warnings potentially fixable with the `--fix` option.

So, the linting looks good to me. I will try to fix theese errors and warnings. Would add tests after this in a seperate pull request.

@pheyvaer Should I ping you once,

  1. The linting errors are sorted.
  2. Most of the coverage is done.?

Copy link
Contributor Author

@pheyvaer pheyvaer Feb 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, in that case

  1. Merge this PR.
  2. Create a new branch were you fix the linting errors. The corresponding issue is Fix linting errors #30
  3. Make a PR with that new branch.
  4. Assign me as a reviewer.

@argahsuknesib argahsuknesib merged commit 74b673e into master Feb 8, 2024
@argahsuknesib argahsuknesib deleted the feature/linting branch February 26, 2024 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants