gitea/web_src/js/components/.eslintrc.yaml

plugins:
  - eslint-plugin-vue

extends:
  - ../../../.eslintrc.yaml
  - plugin:vue/vue3-recommended

env:
  browser: true

rules:
  vue/attributes-order: [0]
  vue/component-definition-name-casing: [0]
  vue/html-closing-bracket-spacing: [0]
  vue/max-attributes-per-line: [0]
  vue/one-component-per-file: [0]
Fix eslint parsing errors, remove eslint-plugin-html (#20323) Introduce a separate .eslintrc in the Vue components folder to selectively enable vue-eslint-parser there, so that the rest of the files can use eslint's core parser which can deal with hashbangs. The fact that the eslint-disable comments worked in HTML was a unintended side-effect of the files being parsed via vue-eslint-parser, so I had to disable the parsing of these files in .eslintrc.yaml to make it work, and finally decided to remove eslint-plugin-html as it causes more issues than it solves. 2022-07-15 11:38:18 +02:00			`plugins:`
			`- eslint-plugin-vue`

			`extends:`
			`- ../../../.eslintrc.yaml`
Update eslints for Vue 3 (#23935) I found that some lint warnings in my editor are conflicting, and I believe the root cause is using lints designed for Vue 2 instead of Vue 3. We moved to Vue 3 in #20044. I verified that the explicitly disabled rules in the changed file are still part of the `vue/vue3-recommended` set. See [Available rules - eslint-plugin-vue](https://eslint.vuejs.org/rules/) for a full list of lints. 2023-04-05 16:59:40 -04:00			`- plugin:vue/vue3-recommended`
Fix eslint parsing errors, remove eslint-plugin-html (#20323) Introduce a separate .eslintrc in the Vue components folder to selectively enable vue-eslint-parser there, so that the rest of the files can use eslint's core parser which can deal with hashbangs. The fact that the eslint-disable comments worked in HTML was a unintended side-effect of the files being parsed via vue-eslint-parser, so I had to disable the parsing of these files in .eslintrc.yaml to make it work, and finally decided to remove eslint-plugin-html as it causes more issues than it solves. 2022-07-15 11:38:18 +02:00
			`env:`
			`browser: true`

			`rules:`
			`vue/attributes-order: [0]`
			`vue/component-definition-name-casing: [0]`
			`vue/html-closing-bracket-spacing: [0]`
			`vue/max-attributes-per-line: [0]`
			`vue/one-component-per-file: [0]`