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
As is mentioned here in the test file, we currently don't identify or auto-fix get on a non-string. This means when the non-string is a variable name, we deem it as valid.
This ticket propose that we identify and auto-fix for those use cases.
Expectations:
obj.get(5) ===> obj[5] // obj.get(5) is legal as I tested.
obj.get(foo) ===> obj[foo]
The text was updated successfully, but these errors were encountered:
ArtixZ
changed the title
New no-get rule and auto-fix
Enhancement - no-get rule and auto-fix
Apr 20, 2023
As is mentioned here in the test file, we currently don't identify or auto-fix
get
on a non-string. This means when the non-string is a variable name, we deem it as valid.This ticket propose that we identify and auto-fix for those use cases.
Expectations:
obj.get(5)
===>obj[5]
//obj.get(5)
is legal as I tested.obj.get(foo)
===>obj[foo]
The text was updated successfully, but these errors were encountered: