allow for vars defined in scope, or within :root/:host selectors in file #294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This expands the
no-undefined-vars
rule to allow for variables that are defined in a local scope, like:This allows developers to use variables defined in locally scoped components, which can be useful for imperatively altering them using the JavaScript APIs, without changing the specific properties they are referred in. So for example this can be useful when using calc or min/max for a specific component:
However this does not allow for undefined vars of a different scope:
It also allows for a file to define its own global variables, which can be either global to the
:host
(for shadow roots) or:root
(for documents). These definitions can only be file local, so the following now works:However specifying variables that exist cross file will still error, unless defined per usual in the rules config: