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.

Sign up for GitHub

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

Jump to bottom

Fix linter warnings #82

Closed
2 of 3 tasks
josecelano opened this issue Jun 21, 2023 · 0 comments · Fixed by #104
Closed
2 of 3 tasks

Fix linter warnings #82

josecelano opened this issue Jun 21, 2023 · 0 comments · Fixed by #104

Comments

@josecelano
Copy link
Member

josecelano commented Jun 21, 2023 •
edited
Loading

When you run the linter, you still see these warnings:

$ npm run lint

> lint
> eslint --ext ".ts,.js,.vue" --ignore-path .gitignore .


/home/josecelano/Documents/git/committer/me/github/torrust/torrust-index-frontend/components/Markdown.vue
  2:22  warning  'v-html' directive can lead to XSS attack  vue/no-v-html

/home/josecelano/Documents/git/committer/me/github/torrust/torrust-index-frontend/components/form/FormInputText.vue
  12:21  warning  The "update:modelValue" event has been triggered but not declared on `defineEmits`  vue/require-explicit-emits

✖ 2 problems (0 errors, 2 warnings)
  • Fix linter warning: 'v-html' directive can lead to XSS attack
  • Fix linter warning: The "update:modelValue" event has been triggered but not declared on defineEmits
  • Add a workflow to run linter on push/pr events
@josecelano josecelano mentioned this issue Jun 21, 2023
Merged
@josecelano josecelano linked a pull request Jun 22, 2023 that will close this issue
Fix linter warnings #104
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Torrust Solution
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix linter warnings
1 participant
@josecelano