fix: make messages more consistent (#11643)

pull/11646/head
Rich Harris 7 months ago committed by GitHub
parent 053159bf0b
commit 3bf68b4765
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

@ -0,0 +1,5 @@
---
'svelte': patch
---
fix: make messages more consistent

@ -174,7 +174,7 @@
## mixed_event_handler_syntaxes
> Mixing old (on:%name%) and new syntaxes for event handling is not allowed. Use only the on%name% syntax.
> Mixing old (on:%name%) and new syntaxes for event handling is not allowed. Use only the on%name% syntax
## node_invalid_placement
@ -230,7 +230,7 @@
## slot_snippet_conflict
> Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely.
> Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely
## snippet_conflict

@ -20,7 +20,7 @@
## a11y_click_events_have_key_events
> Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type="button">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.
> Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type="button">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details
## a11y_distracting_elements
@ -40,7 +40,7 @@
## a11y_img_redundant_alt
> Screenreaders already announce `<img>` elements as an image.
> Screenreaders already announce `<img>` elements as an image
## a11y_incorrect_aria_attribute_type
@ -76,7 +76,7 @@
## a11y_interactive_supports_focus
> Elements with the '%role%' interactive role must have a tabindex value.
> Elements with the '%role%' interactive role must have a tabindex value
## a11y_invalid_attribute
@ -84,7 +84,7 @@
## a11y_label_has_associated_control
> A form label must be associated with a control.
> A form label must be associated with a control
## a11y_media_has_caption
@ -120,7 +120,7 @@
## a11y_no_noninteractive_element_interactions
> Non-interactive element `<%element%>` should not be assigned mouse or keyboard event listeners.
> Non-interactive element `<%element%>` should not be assigned mouse or keyboard event listeners
## a11y_no_noninteractive_element_to_interactive_role

@ -32,8 +32,8 @@
## event_directive_deprecated
> Using `on:%name%` to listen to the %name% event is deprecated. Use the event attribute `on%name%` instead.
> Using `on:%name%` to listen to the %name% event is deprecated. Use the event attribute `on%name%` instead
## slot_element_deprecated
> Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead.
> Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead

@ -928,13 +928,13 @@ export function let_directive_invalid_placement(node) {
}
/**
* Mixing old (on:%name%) and new syntaxes for event handling is not allowed. Use only the on%name% syntax.
* Mixing old (on:%name%) and new syntaxes for event handling is not allowed. Use only the on%name% syntax
* @param {null | number | NodeLike} node
* @param {string} name
* @returns {never}
*/
export function mixed_event_handler_syntaxes(node, name) {
e(node, "mixed_event_handler_syntaxes", `Mixing old (on:${name}) and new syntaxes for event handling is not allowed. Use only the on${name} syntax.`);
e(node, "mixed_event_handler_syntaxes", `Mixing old (on:${name}) and new syntaxes for event handling is not allowed. Use only the on${name} syntax`);
}
/**
@ -1059,12 +1059,12 @@ export function slot_element_invalid_name_default(node) {
}
/**
* Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely.
* Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely
* @param {null | number | NodeLike} node
* @returns {never}
*/
export function slot_snippet_conflict(node) {
e(node, "slot_snippet_conflict", "Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely.");
e(node, "slot_snippet_conflict", "Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely");
}
/**

@ -137,11 +137,11 @@ export function a11y_autofocus(node) {
}
/**
* Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type="button">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.
* Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type="button">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details
* @param {null | NodeLike} node
*/
export function a11y_click_events_have_key_events(node) {
w(node, "a11y_click_events_have_key_events", "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.");
w(node, "a11y_click_events_have_key_events", "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details");
}
/**
@ -179,11 +179,11 @@ export function a11y_hidden(node, name) {
}
/**
* Screenreaders already announce `<img>` elements as an image.
* Screenreaders already announce `<img>` elements as an image
* @param {null | NodeLike} node
*/
export function a11y_img_redundant_alt(node) {
w(node, "a11y_img_redundant_alt", "Screenreaders already announce `<img>` elements as an image.");
w(node, "a11y_img_redundant_alt", "Screenreaders already announce `<img>` elements as an image");
}
/**
@ -262,12 +262,12 @@ export function a11y_incorrect_aria_attribute_type_tristate(node, attribute) {
}
/**
* Elements with the '%role%' interactive role must have a tabindex value.
* Elements with the '%role%' interactive role must have a tabindex value
* @param {null | NodeLike} node
* @param {string} role
*/
export function a11y_interactive_supports_focus(node, role) {
w(node, "a11y_interactive_supports_focus", `Elements with the '${role}' interactive role must have a tabindex value.`);
w(node, "a11y_interactive_supports_focus", `Elements with the '${role}' interactive role must have a tabindex value`);
}
/**
@ -281,11 +281,11 @@ export function a11y_invalid_attribute(node, href_value, href_attribute) {
}
/**
* A form label must be associated with a control.
* A form label must be associated with a control
* @param {null | NodeLike} node
*/
export function a11y_label_has_associated_control(node) {
w(node, "a11y_label_has_associated_control", "A form label must be associated with a control.");
w(node, "a11y_label_has_associated_control", "A form label must be associated with a control");
}
/**
@ -363,12 +363,12 @@ export function a11y_no_interactive_element_to_noninteractive_role(node, element
}
/**
* Non-interactive element `<%element%>` should not be assigned mouse or keyboard event listeners.
* Non-interactive element `<%element%>` should not be assigned mouse or keyboard event listeners
* @param {null | NodeLike} node
* @param {string} element
*/
export function a11y_no_noninteractive_element_interactions(node, element) {
w(node, "a11y_no_noninteractive_element_interactions", `Non-interactive element \`<${element}>\` should not be assigned mouse or keyboard event listeners.`);
w(node, "a11y_no_noninteractive_element_interactions", `Non-interactive element \`<${element}>\` should not be assigned mouse or keyboard event listeners`);
}
/**
@ -698,18 +698,18 @@ export function element_invalid_self_closing_tag(node, name) {
}
/**
* Using `on:%name%` to listen to the %name% event is deprecated. Use the event attribute `on%name%` instead.
* Using `on:%name%` to listen to the %name% event is deprecated. Use the event attribute `on%name%` instead
* @param {null | NodeLike} node
* @param {string} name
*/
export function event_directive_deprecated(node, name) {
w(node, "event_directive_deprecated", `Using \`on:${name}\` to listen to the ${name} event is deprecated. Use the event attribute \`on${name}\` instead.`);
w(node, "event_directive_deprecated", `Using \`on:${name}\` to listen to the ${name} event is deprecated. Use the event attribute \`on${name}\` instead`);
}
/**
* Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead.
* Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead
* @param {null | NodeLike} node
*/
export function slot_element_deprecated(node) {
w(node, "slot_element_deprecated", "Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead.");
w(node, "slot_element_deprecated", "Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead");
}

@ -4,7 +4,7 @@ export default test({
error: {
code: 'slot_snippet_conflict',
message:
'Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely.',
'Cannot use `<slot>` syntax and `{@render ...}` tags in the same component. Migrate towards `{@render ...}` tags completely',
position: [71, 84]
}
});

@ -1,7 +1,7 @@
[
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 13,
"column": 0
@ -13,7 +13,7 @@
},
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 15,
"column": 0
@ -25,7 +25,7 @@
},
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 18,
"column": 0
@ -37,7 +37,7 @@
},
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 20,
"column": 0
@ -49,7 +49,7 @@
},
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 22,
"column": 0
@ -61,7 +61,7 @@
},
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 24,
"column": 0
@ -73,7 +73,7 @@
},
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 26,
"column": 0
@ -85,7 +85,7 @@
},
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"line": 28,
"column": 0

@ -1,7 +1,7 @@
[
{
"code": "a11y_img_redundant_alt",
"message": "Screenreaders already announce `<img>` elements as an image.",
"message": "Screenreaders already announce `<img>` elements as an image",
"end": {
"column": 49,
"line": 3
@ -13,7 +13,7 @@
},
{
"code": "a11y_img_redundant_alt",
"message": "Screenreaders already announce `<img>` elements as an image.",
"message": "Screenreaders already announce `<img>` elements as an image",
"end": {
"column": 45,
"line": 4
@ -25,7 +25,7 @@
},
{
"code": "a11y_img_redundant_alt",
"message": "Screenreaders already announce `<img>` elements as an image.",
"message": "Screenreaders already announce `<img>` elements as an image",
"end": {
"column": 52,
"line": 5

@ -5,7 +5,7 @@
"column": 48,
"line": 11
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 11
@ -17,7 +17,7 @@
"column": 51,
"line": 12
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 12
@ -29,7 +29,7 @@
"column": 45,
"line": 13
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 13
@ -41,7 +41,7 @@
"column": 72,
"line": 14
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 14
@ -53,7 +53,7 @@
"column": 51,
"line": 15
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 15
@ -65,7 +65,7 @@
"column": 52,
"line": 16
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 16
@ -77,7 +77,7 @@
"column": 44,
"line": 17
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 17
@ -89,7 +89,7 @@
"column": 51,
"line": 18
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 18
@ -101,7 +101,7 @@
"column": 49,
"line": 19
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 19
@ -113,7 +113,7 @@
"column": 52,
"line": 20
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 20
@ -125,7 +125,7 @@
"column": 49,
"line": 21
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 21
@ -137,7 +137,7 @@
"column": 52,
"line": 22
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 22
@ -149,7 +149,7 @@
"column": 49,
"line": 23
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 23
@ -161,7 +161,7 @@
"column": 48,
"line": 24
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 24
@ -173,7 +173,7 @@
"column": 49,
"line": 25
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 25
@ -185,7 +185,7 @@
"column": 54,
"line": 26
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 26
@ -197,7 +197,7 @@
"column": 50,
"line": 27
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 27
@ -209,7 +209,7 @@
"column": 53,
"line": 28
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 28
@ -221,7 +221,7 @@
"column": 48,
"line": 29
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 29
@ -245,7 +245,7 @@
"column": 53,
"line": 30
},
"message": "Elements with the 'menuitem' interactive role must have a tabindex value.",
"message": "Elements with the 'menuitem' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 30
@ -269,7 +269,7 @@
"column": 47,
"line": 31
},
"message": "Elements with the 'button' interactive role must have a tabindex value.",
"message": "Elements with the 'button' interactive role must have a tabindex value",
"start": {
"column": 0,
"line": 31

@ -5,7 +5,7 @@
"column": 16,
"line": 5
},
"message": "A form label must be associated with a control.",
"message": "A form label must be associated with a control",
"start": {
"column": 0,
"line": 5
@ -17,7 +17,7 @@
"column": 30,
"line": 10
},
"message": "A form label must be associated with a control.",
"message": "A form label must be associated with a control",
"start": {
"column": 0,
"line": 10

@ -5,7 +5,7 @@
"column": 51,
"line": 10
},
"message": "Non-interactive element `<div>` should not be assigned mouse or keyboard event listeners.",
"message": "Non-interactive element `<div>` should not be assigned mouse or keyboard event listeners",
"start": {
"column": 0,
"line": 10
@ -17,7 +17,7 @@
"column": 58,
"line": 11
},
"message": "Non-interactive element `<h1>` should not be assigned mouse or keyboard event listeners.",
"message": "Non-interactive element `<h1>` should not be assigned mouse or keyboard event listeners",
"start": {
"column": 0,
"line": 11
@ -29,7 +29,7 @@
"column": 50,
"line": 12
},
"message": "Non-interactive element `<h1>` should not be assigned mouse or keyboard event listeners.",
"message": "Non-interactive element `<h1>` should not be assigned mouse or keyboard event listeners",
"start": {
"column": 0,
"line": 12
@ -41,7 +41,7 @@
"column": 30,
"line": 13
},
"message": "Non-interactive element `<p>` should not be assigned mouse or keyboard event listeners.",
"message": "Non-interactive element `<p>` should not be assigned mouse or keyboard event listeners",
"start": {
"column": 0,
"line": 13
@ -53,7 +53,7 @@
"column": 50,
"line": 14
},
"message": "Non-interactive element `<div>` should not be assigned mouse or keyboard event listeners.",
"message": "Non-interactive element `<div>` should not be assigned mouse or keyboard event listeners",
"start": {
"column": 0,
"line": 14

@ -301,7 +301,7 @@
},
{
"code": "a11y_label_has_associated_control",
"message": "A form label must be associated with a control.",
"message": "A form label must be associated with a control",
"start": {
"line": 28,
"column": 0

@ -1,7 +1,7 @@
[
{
"code": "mixed_event_handler_syntaxes",
"message": "Mixing old (on:click) and new syntaxes for event handling is not allowed. Use only the onclick syntax.",
"message": "Mixing old (on:click) and new syntaxes for event handling is not allowed. Use only the onclick syntax",
"start": {
"line": 11,
"column": 8

@ -5,7 +5,7 @@
"column": 13,
"line": 10
},
"message": "Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead.",
"message": "Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead",
"start": {
"column": 0,
"line": 10
@ -17,7 +17,7 @@
"column": 24,
"line": 11
},
"message": "Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead.",
"message": "Using `<slot>` to render parent content is deprecated. Use `{@render ...}` tags instead",
"start": {
"column": 0,
"line": 11
@ -29,7 +29,7 @@
"column": 22,
"line": 12
},
"message": "Using `on:click` to listen to the click event is deprecated. Use the event attribute `onclick` instead.",
"message": "Using `on:click` to listen to the click event is deprecated. Use the event attribute `onclick` instead",
"start": {
"column": 8,
"line": 12

@ -1,7 +1,7 @@
[
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"column": 1,
"line": 7

@ -1,7 +1,7 @@
[
{
"code": "a11y_click_events_have_key_events",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details.",
"message": "Visible, non-interactive elements with a click event must be accompanied by a keyboard event handler. Consider whether an interactive element such as `<button type=\"button\">` or `<a>` might be more appropriate. See https://svelte.dev/docs/accessibility-warnings#a11y-click-events-have-key-events for more details",
"start": {
"column": 1,
"line": 8

Loading…
Cancel
Save