You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been using eslint-plugin-vue-a11y and now running with an issue . I have created a form Input component which dynamically accepts the TYPE (text,number,email etc..) . Below is the code that i'm using which works fine but showing error from vue-a11y .
CODE :
<input
v-model="inputValue"
:maxlength="maxLength"
:minLength="minLength" :type="inputType". ===> here is the prob
:class="$style.input" @Focus="handleFocus(true)" @blur="handleFocus(false)" @keypress="keyPressValidation($event)"
/>
So i understood that since i haven't added any specific TYPE to the Input , this issue is happening . So all i want is to ignore this and proceed , but i just don't find any way to do that .
Here is the error i am getting :
TypeError: value.toUpperCase is not a function
Occurred while linting /base/form-input.vue:2
at Object.isHiddenFromScreenReader (/node_modules/eslint-plugin-vue-a11y/lib/utils/index.js:84:30)
at EventEmitter.VElement (/node_modules/eslint-plugin-vue-a11y/lib/rules/interactive-supports-focus.js:42:22)
at EventEmitter.emit (events.js:203:15)
at NodeEventGenerator.applySelector (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:3274:26)
at NodeEventGenerator.applySelectors (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:3288:22)
at NodeEventGenerator.enterNode (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:3296:14)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:113:13)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:120:21)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:120:21)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:120:21)
Please let me know a way to either ignore and proceed or add some support accordingly.
The text was updated successfully, but these errors were encountered:
Hey there ,
I have been using eslint-plugin-vue-a11y and now running with an issue . I have created a form Input component which dynamically accepts the TYPE (text,number,email etc..) . Below is the code that i'm using which works fine but showing error from vue-a11y .
CODE :
<input
v-model="inputValue"
:maxlength="maxLength"
:minLength="minLength"
:type="inputType". ===> here is the prob
:class="$style.input"
@Focus="handleFocus(true)"
@blur="handleFocus(false)"
@keypress="keyPressValidation($event)"
/>
So i understood that since i haven't added any specific TYPE to the Input , this issue is happening . So all i want is to ignore this and proceed , but i just don't find any way to do that .
Here is the error i am getting :
TypeError: value.toUpperCase is not a function
Occurred while linting /base/form-input.vue:2
at Object.isHiddenFromScreenReader (/node_modules/eslint-plugin-vue-a11y/lib/utils/index.js:84:30)
at EventEmitter.VElement (/node_modules/eslint-plugin-vue-a11y/lib/rules/interactive-supports-focus.js:42:22)
at EventEmitter.emit (events.js:203:15)
at NodeEventGenerator.applySelector (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:3274:26)
at NodeEventGenerator.applySelectors (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:3288:22)
at NodeEventGenerator.enterNode (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:3296:14)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:113:13)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:120:21)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:120:21)
at traverse (/node_modules/eslint-plugin-vue-a11y/node_modules/vue-eslint-parser/index.js:120:21)
Please let me know a way to either ignore and proceed or add some support accordingly.
The text was updated successfully, but these errors were encountered: