Skip to content
New issue

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

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

Already on GitHub? # to your account

ci: added eslint checks for ui #244

Merged
merged 7 commits into from
Feb 19, 2024
Merged

ci: added eslint checks for ui #244

merged 7 commits into from
Feb 19, 2024

Conversation

raaymax
Copy link
Collaborator

@raaymax raaymax commented Feb 15, 2024

On previous PR we lost some time fixing issues that should be handled by linter.
I checked and noticed that eslint was not working in the project so i fixed it.
Additionally added GH actions workflow for lint checking

@ramedina86
Copy link
Collaborator

Sounds great, @FabienArcellier thoughts?

@raaymax What were the issues from the previous PR that the linter would have caught? (just curious)

@raaymax
Copy link
Collaborator Author

raaymax commented Feb 15, 2024

Now as I review this PR, there isn't really much there. Actually, just console.log. Anyway, in the meantime, I fixed more things on my own, which is why it seemed like there was more.

@raaymax
Copy link
Collaborator Author

raaymax commented Feb 15, 2024

From all this changes I only added missing :key bindings in v-for directives and some ignore comments. The rest was made by eslint . --fix

@ramedina86
Copy link
Collaborator

Hey @raaymax are we good to merge this?

@raaymax
Copy link
Collaborator Author

raaymax commented Feb 19, 2024

If @FabienArcellier doesn't have any more comments, then yes.

@ramedina86 ramedina86 merged commit 7f6815e into writer:dev Feb 19, 2024
12 checks passed
@raaymax raaymax deleted the eslint-fix branch February 20, 2024 08:10
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants