Add option for custom symbles to no-top-level-browser-globals
#1234
Labels
enhancement
New feature or request
no-top-level-browser-globals
#1234
Description
Say I have a custom function that wraps a browser global for example
getCookieValue
. This function shouldn't be used at the top level due to the use of a browser global butno-top-level-browser-globals
has no way to know that.I propose an option for the rule that allows the user to define additional symbols that should be checked for.
The text was updated successfully, but these errors were encountered: