Goto Symbol (ctrl+r) doesn't work for methods of anonymous object

[YuriGor]

test({
  myMethod:function(){
    console.info("I want this method be listed in functions list too!");
    console.warn("In native 'JavaScript' syntax it is!");
  }
});

Ctrl+R doesn't work for code sample above.
It's a most most used construction for ExtJS app:

Ext.create('Ext.Button', {
    text: 'Click me',
    renderTo: Ext.getBody(),
    handler: function() {
        alert('You clicked the button!');
    }
});

Babel syntax package does not respect such methods too, this is why I tried to switch to Naomi.

[borela]

Fixed https://github.com/borela/naomi/releases/tag/v4.2.5

[YuriGor]

Still doesn't work

[YuriGor]

For test I installed Naomi from latest master from github

[YuriGor]

also this is from sublime's console:

Packages/Naomi/syntaxes/naomi.fjsx15.sublime-syntax: context Packages/Naomi/syntaxes/fjsx15/destructuring/object/property.sublime-syntax#meta-destructuring has a scope name, but is unreachable, so the name will never be used

As I remember, same warning was before this commit too.

[borela]

Clean the cache directory to force sublime to recompile the syntaxes:

• OS X: ~/Library/Application Support/Sublime Text 3
• Windows: %LOCALAPPDATA%\Sublime Text 3
• Linux: ~/.config/sublime-text-3

And restart sublime.

Packages/Naomi/syntaxes/naomi.fjsx15.sublime-syntax: context Packages/Naomi/syntaxes/fjsx15/destructuring/object/property.sublime-syntax#meta-destructuring has a scope name, but is unreachable, so the name will never be used

You can ignore that warning for now, I do use that context in an external file, the problem is that the sublime's syntax system was not planned to work with multiple files like I did, that'll be fixed when I finish the build system where the files will be concatenated into a single one, it should also improve the speed.

[YuriGor]

I closed subl, emptied /home/gor/.config/sublime-text-3/Cache and started subl, still doesn't work (

[YuriGor]

may be some other plugin do this, native js syntax stopped to work too, need to investigate

[YuriGor]

I removed some packages including babel, now Naomi started to work, but incorrect:

For each method it shows two lines, first one is function name and second is parentheses
compare with native JS:

[borela]

Yes, the meta.declaration.function scopes were incorrect and causing the issue, I sent a patch to the master branch, this should be the result:

[borela]

I also tagged the commit https://github.com/borela/naomi/releases/tag/v4.2.6, so if you are using the package control's version instead of clonning, you should see the update in ~2 hours.

[YuriGor]

I tested fresh version from github, now it works correctly, thank you!

[borela]

Thank you for reporting this issue, I knew something odd was happenning but was only able to pin point the issue after your report. Feel free to open more of them as soon as you find more bugs.

[YuriGor]

Ok, I already have issue about coloring, but need some time to prepare screenshots to show difference with native JS syntax highlighting for different color schemes:
looks like object field names was categorized some incorrect way.
In native JS syntax they are semi-white both in monokai and candyman
but with Naomiin they are yellow as string in monokai or green in candyman (look screenshots above for example)
I'd better open new issue to add some details if I'll find them