Inconsistency for Ruby 1.9 symbol
See original GitHub issueThank you for solving the ruby color for symbol. It would be great if you can do one more change for an alternative symbol syntax for Ruby 1.9+
:one => 1 # normal form
one: 1 # ruby 1.9+
So it is still inconsistent. And even the function args look different as well:) Atom:
One Dark Pro:
_Originally posted by @foreverqihe in https://github.com/Binaryify/OneDark-Pro/issues/258#issuecomment-427642264_
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Inconsistent documentation regarding parameter validation
Documentation is inconsistent with regards to parameter validation. ... The => is a Ruby 1.8.7 syntax, which was replaced by : in Ruby...
Read more >Update your entire project to Ruby 1.9 hash syntax
Update your entire project to Ruby 1.9 hash syntax. In version 1.9 Ruby introduced new syntax for hash literals whose keys are symbols....
Read more >Feature #5607: Inconsistent reaction in Range of String
Description. =begin. When I tried to access excel file, I found some inconsistent behavior about range of string. ruby-1.9.3-p0 :001 > ("A".."AB").to_a
Read more >Is Hash Rocket deprecated? - ruby - Stack Overflow
1 Answer 1 · You must use the rocket for symbols that are not valid labels: :$set => x is valid but $set:...
Read more >Class: Struct (Ruby 1.9.1)
A Struct is a convenient way to bundle a number of attributes together, using accessor methods, without having to write an explicit class....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Alright I get it now. Thanks for the help.
When installing the Ruby extension on VSCode, it creates additional scopes that native VSCode does not have. Of these scopes which are relevant to your issue, are:
variable
andconstant
. Since One Dark Pro only really supports the languages’ prebuilt scopes (and Ruby never provided them in the first place), the default highlighting for these scopes will just come into effect. As such the defaultvariable
is that red colour and the defaultconstant
is that yellowish-orange.Now I haven’t investigated Atom completely, but it seems the Ruby language doesn’t define those
variable
andconstant
scopes like VSCode, hence it uses that highlighting shown in your first screenshot. You might then suggest to incorporate this change but that’d be up to @Binaryify as it is extension-related rather than prebuilt. You could always fork and open a pull request, or I could… Either is fine, but he has the final say :>Hope this helps!
Thank you for the investigation. Would you mind letting me know how to do it in the settings.json, if it doesn’t take too much time for you?