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.

Misleading variable name in the migration guide

See original GitHub issue

Describe the bug

The migration guide uses the variable name v$. This is misleading because the 0.x version used $v. After the migration, I couldn’t figure out why the errors occurred for a long time.

 setup () {
    return { v$: useVuelidate() }
  },

https://vuelidate-next.netlify.app/migration_guide.html

Expected behavior You can add a new paragraph to the migration about renaming the variable, but do it explicitly.

Issue Analytics

State:
Created a year ago
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

dobromir-hristovcommented, May 1, 2022

WDYT? Is this enough in the migration guide?

2reactions

dobromir-hristovcommented, May 1, 2022

Oh I see what you mean. Make it explicit with a warning for Vue 2 users? Yep will do!

Top Results From Across the Web

Migrating from the "engine" option - Apollo GraphQL Docs

Apollo Server v2.18 deprecates the engine option to the ApolloServer constructor and provides a new way of configuring its communication with Apollo Studio....

Variables Guide — os-migrate documentation - GitHub Pages

The goal of this document is to guide users to correctly configure the most important variables in OS Migrate. For a complete listing...

Runtime Changes for Migration from .NET Framework 4.7.2 to ...

Method 1: Environment variable This method affects any environment that inherits this environment variable. This might be just a single console ...

Backward Incompatible Changes - Manual - PHP

Some "Only variables should be passed by reference" notices have been converted to "Argument cannot be passed by reference" exception. The generated name...

Migration Guide - Spock Framework

Assert unroll expressions by default This means tests that were successful but had an #Error: name rendering will now fail. It can be...