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
{{ message }}
This repository was archived by the owner on Dec 15, 2022. It is now read-only.
although author&.posts is sort of used as a shorthand of author && author.posts, they're different in that it only skips the invocations on nil but not false
"logical" is shaky even for && for that it's essentially a flow control operator in Ruby (so as &.)
Is there any way to make progress with this? I don't have syntax highlighting for safe navigation operators in VSCode which uses this language server. Considering this is a few years old, it would be nice!
Activity
hediyi commentedon Sep 23, 2016
I think "logical" is a bad scope name for
&.
:author&.posts
is sort of used as a shorthand ofauthor && author.posts
, they're different in that it only skips the invocations onnil
but notfalse
&&
for that it's essentially a flow control operator in Ruby (so as&.
).
part in itbbugh commentedon Jul 11, 2019
Is there any way to make progress with this? I don't have syntax highlighting for safe navigation operators in VSCode which uses this language server. Considering this is a few years old, it would be nice!
Change Textmate scope for safe navigation operator. Resolves #288
jmoglesby commentedon Apr 4, 2021
This issue was addressed for the
vscode-ruby
library, but it still has not been addressed for theatom/language-ruby
library.Here was the
vscode-ruby
solution, which I believe is still using TextMate:Can we get this applied to the Tree-sitter version for Atom, so that Safe Nav operators can be highlighted as operators, rather than as methods?