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
Packages/Svelte/tests/syntax_test_scope.svelte:153:30
error: scope does not match
153 | <li><span>{id}</span><MyComponent {...rest} /></li>
159 | | ^^^^^^^^^^^ entity.name.tag.inline.form.html
| ^^^^^^^^^^^ these locations did not match
actual:
| ^^^^^^^^^^^ text.html.svelte meta.tag.component.html entity.name.tag.component.svelte
FAILED: 1 of 182 assertions in 1 files failed
[Finished]
Steps to reproduce
Create a failing syntax test case
Navigate to it via F4
Expected behavior
Column of failure should be 31 and caret should be located in front of MyComponent after navigating to it via F4 key.
Actual behavior
The error is the MyComponent token being mis-scoped.
Syntax error says it begins on column 30 and status bar says it placed caret on column 30 after navigating via F4.
Caret is however located in front of <.
Sublime Text build number
4183
Operating system & version
Windows 11
(Linux) Desktop environment and/or window manager
No response
Additional information
No response
OpenGL context information
No response
The text was updated successfully, but these errors were encountered:
Description of the bug
I have a feeling, new syntax test outputs test failures with one char off.
syntax test case
syntax test output
Steps to reproduce
F4
Expected behavior
Column of failure should be 31 and caret should be located in front of
MyComponent
after navigating to it via F4 key.Actual behavior
The error is the
MyComponent
token being mis-scoped.Syntax error says it begins on column 30 and status bar says it placed caret on column 30 after navigating via F4.
Caret is however located in front of
<
.Sublime Text build number
4183
Operating system & version
Windows 11
(Linux) Desktop environment and/or window manager
No response
Additional information
No response
OpenGL context information
No response
The text was updated successfully, but these errors were encountered: