Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add JavaScript linting and GitHub workflow for testing #310

Merged
merged 3 commits into from
Nov 20, 2024

Conversation

KristjanESPERANTO
Copy link
Collaborator

To continue tackling issue #297, I'm adding JavaScript linting and a GitHub workflow that runs the linting and spelling tests on every push and pull request.

I've deliberately set soft linting rules. If I set harder rules, the resulting code changes would certainly cause ugly merge conflicts of old pull requests.
We can make the linter rules harder after we have dealt with the old pull requests.

@ezeholz
Copy link
Collaborator

ezeholz commented Nov 19, 2024

I'm seeing a few warnings on the code, made by run-lint.
Should we fix them?

@KristjanESPERANTO
Copy link
Collaborator Author

We could easily fix them, but then we would have problems with merging some older pull requests. My plan was to deal with the warnings later. But we can pursue a different strategy and take care of this linter issues now. I would also agree to that 🙂

@ezeholz
Copy link
Collaborator

ezeholz commented Nov 19, 2024

I see!

I propose to merge this PR and the olders that seems worth to have. And making the next step to fix the linter.
We shouldn't be procrastinating those fixes too much, as that may generate a snowball effect.

Maybe after the fix, we can plan a release, and come back with testings after it.

How does that sound to you?

@KristjanESPERANTO
Copy link
Collaborator Author

Sounds good! 😃

@KristjanESPERANTO
Copy link
Collaborator Author

@ezeholz I suggest to merge this PR and #305 and then do a minor release 🙂

@ezeholz
Copy link
Collaborator

ezeholz commented Nov 20, 2024

Cool! I'll merge them then ✨️

@ezeholz ezeholz merged commit 01d8e79 into Jopyth:develop Nov 20, 2024
1 check passed
@ezeholz ezeholz mentioned this pull request Nov 20, 2024
@KristjanESPERANTO KristjanESPERANTO deleted the linter branch November 21, 2024 00:39
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.

2 participants