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
I've started to find the "Go to Symbol" prompt to be extremely useful. Unfortunately, there are a lot of problem cases with it. It seems to treat : and = interchangeably everywhere (not just in a class), so
a = -> b: ->
gives you
a
b
but
c = -> {d: ->}
gives you
c
d
Neither seems very sensible to me; functions in objects (other than class prototypes) should be ignored, the way that functions given as callbacks are. Don't you think? Or is it more important to list every function that's assigned a symbol than to present a clean hierarchy? Keep in mind that the current behavior means that if you write
That's a really good question, and unfortunately one that depends greatly on the style of JavaScript you're going to be writing. I think that showing every function with a name in the symbol list by default is a good start.
I've started to find the "Go to Symbol" prompt to be extremely useful. Unfortunately, there are a lot of problem cases with it. It seems to treat
:
and=
interchangeably everywhere (not just in aclass
), sogives you
but
gives you
Neither seems very sensible to me; functions in objects (other than
class
prototypes) should be ignored, the way that functions given as callbacks are. Don't you think? Or is it more important to list every function that's assigned a symbol than to present a clean hierarchy? Keep in mind that the current behavior means that if you writethen you'll see "click" 5 times in the "Go to Symbol" list.
The text was updated successfully, but these errors were encountered: