Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Suggestion: experimental feature should be disabled by default

See original GitHub issue

In recent case ( v0.19.0 , v0.19.1 ) it would be

"vetur.experimental.templateInterpolationService": false

An experimental feature which is not fully battle tested might confuse users when things are not going well.

Features in this stage should be able to be manually turned on, usually by people who know what they are doing, and/or have a need for the certain feature. And they can help you test the feature before it is ready to be enabled by default.

Issue Analytics

State:
Created 4 years ago
Reactions:21
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

octrefcommented, Apr 26, 2019

I disabled it by default because upstream issues like https://github.com/vuejs/vetur/issues/1226 is not solvable through types yet, and mapGetters from vuex can’t add members to this either.

1reaction

protodonutscommented, Apr 26, 2019

How would I battle test experimental features?

You may git clone some random, active, seems-well-maintained vue projects on GitHub, open them with your new release candidate. And compare it with your last stable release?

Before major release at least have some look from the perspective of the end users.