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
Let the Code run. The Error that there is no :key for this template should happen on Compile time.
What is expected?
The template got replaced with each html tag inside the temlate.
This expected behavior worked fine in vue@3.0.0-0
What is actually happening?
The Message sais you should place the key into the template tag.
If you place the key into the template tag there is an error that you are not allowed to place a key tag there.
If you replace the template tag with a div and the key tag into the div everything works fine, but the extra div is renderd into the dom.
I have two elements, which i want to render for each iteration without any suraunding structure.
It worked fine until i upgraded the packages and was suprised this changed.
The text was updated successfully, but these errors were encountered:
This is a known issue in eslint-plugin-vue: vuejs/eslint-plugin-vue#1279
Will require a new release of it for this to be fixed. For now, you can disable the related rules in your eslint config.
Version
3.0.0-rc.7
Reproduction link
https://github.com/Jona898/vue-next---Bug-require-key-in-template
Steps to reproduce
Let the Code run. The Error that there is no :key for this template should happen on Compile time.
What is expected?
The template got replaced with each html tag inside the temlate.
This expected behavior worked fine in vue@3.0.0-0
What is actually happening?
The Message sais you should place the key into the template tag.
If you place the key into the template tag there is an error that you are not allowed to place a key tag there.
If you replace the template tag with a div and the key tag into the div everything works fine, but the extra div is renderd into the dom.
I have two elements, which i want to render for each iteration without any suraunding structure.
It worked fine until i upgraded the packages and was suprised this changed.
The text was updated successfully, but these errors were encountered: