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
(Sigh, I noticed in the "Preview" view that the code that I copy/pasted into the code sections is all messed up. I have attached screen shots below so you can see what I have.)
I have the following template in a .vue component. Notice the JS-style comment in the middle.
<template>
<div>
<b-tablesmallstripedhoverfoot-clone:items="solutions":fields="columns":filter="filter"@row-clicked="rowClicked">
<template
slot="top-row"
slot-scope="{columns, fields}">
{{ /* columns and fields are properties passed in from the table to the template.
columns is the number of columns.
fields is an array of column names
*/ }}
<tdv-for="(column) of fields":key="column.key">
<ColumnFilter:column="column" />
</td>
</template>
</b-table>
</div>
</template>
I am getting the following error from eslint, referencing the last line of the comment.
Parsing error: Unexpected end of expression. (vue/no-parsing-error) (25,12)
The squiqqly error indicator is under the first "}" character of the closing "}}".
I believe this is not an error.
The text was updated successfully, but these errors were encountered:
(Sigh, I noticed in the "Preview" view that the code that I copy/pasted into the code sections is all messed up. I have attached screen shots below so you can see what I have.)
Environment:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
node v6.11.3
VSCode version 1.20.0
.eslintrc.json:
I have the following template in a .vue component. Notice the JS-style comment in the middle.
I am getting the following error from eslint, referencing the last line of the comment.
Parsing error: Unexpected end of expression. (vue/no-parsing-error) (25,12)
The squiqqly error indicator is under the first "}" character of the closing "}}".
I believe this is not an error.
The text was updated successfully, but these errors were encountered: