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
The existing validation logic currently aids users by reporting references to undeclared variables, such as below.
There can be different reasons behind an "orphaned" reference (reference without corresponding declaration). It could be a result of an intentional removal. But it can also be because the user started using variable reference before declaring it.
The server could help in the latter case by generating the local value declaration for the user.
Provide quickfix code action for any undeclared local.* references which will generate locals entry with the empty value based on constraints surrounding the reference
The text was updated successfully, but these errors were encountered:
Background
The existing validation logic currently aids users by reporting references to undeclared variables, such as below.
There can be different reasons behind an "orphaned" reference (reference without corresponding declaration). It could be a result of an intentional removal. But it can also be because the user started using variable reference before declaring it.
The server could help in the latter case by generating the local value declaration for the user.
For example, user may start with:
and want to end up with:
Proposal
quickfix
code action for any undeclaredlocal.*
references which will generatelocals
entry with the empty value based on constraints surrounding the referenceThe text was updated successfully, but these errors were encountered: