Does this support folding on the description line of a JSDoc comment?

For example, I'd expect the following comment:

/**
 * Returns a random timestamp between 1900 and today's date.
 *
 * @return {int} A timestamp in Unix time format
 */

... to show the following when folded:

-- 5 lines: Returns a random timestamp between 1900 and today's date.

... whereas, it's currently displayed as:

-- 5 lines: *

Not sure if this is a feature but if it is, I would love to be able to customize it.

Code inside functions is indented according to where the first letter of function is. This leads to a not constant indentation that depends on methods name.

var a = {
    b: function(){
           return;
       },
    hello: function(){
               return;
           }
}

Object methods defined without function are not being highlighted:

{
  doSomething() {
    // ...
  }
}

(unless I'm missing it somewhere...)

What would I do to test?
Please add to readme

javaScriptFuncKeyword is highlighting incorrectly when the same theme is compared with Atom and Sublime packages of the same themes.

Hey guys,

I am having problems with the code folding feature that apparently opens up all folded structures when editing the code. i.e: when creating a new function and typing the opening curly brace, all the remaining folds are then opened and I am required to re-close them with zx. The same happens with if statements when typing the closing curly brace.

As per the instructions shown on the README file, my ~/.vimrc file contains:

au FileType javascript call JavaScriptFold()

Here is a demo of the current behaviour:

If someone could point a workaround that it would be appreciated.
Thanks in advance

If a line contains a slash and a comment, the plugin highlights the text from the slash to the comment as a regex, then fails to highlight the comment.

var result = 1 / 2; // this is a comment, but it won't be highlighted
var block = 2 / 3; /* this also will consider /3;/ as a regex */

these 3 words are not reserved in theory but it used as reserved so vim really should just highlight them.

Hi. I installed via Pathogen, but I don't have any syntax hightlighting. Nothing happened...

Is there something else I need to do as well to get it to work??

For YUI there is the following repo:

https://github.com/yui/editor-extras

Hope that helps.

Testing code:

var a = [
    '<div class="main">',
        'The result is:<strong>', iTotal/iParts, '</strong>.'
    '</div>'
].join('');

The syntax highlight broke by the /.

This is what I'm seeing:

I've tried this with a handful of themes using version c907b15. Is anyone else seeing highlighted template strings? It looks like this feature was added in #51.

It seems that method shorthand syntax for object breaks highlights of its body.

In this screenshot, if is highlighted as invalid.

Code:

const a = {
    "foo"() {
        if (true) {}
    }
};

Environment:

• OS X 10.11
• Vim 8.0-3
• vim-javascript-syntax: 9e019fc

Is there any way to configure this to also work with typescript?

Title says it all. I'm working on this!

I love this plugin, btw.

Just wanted to mention that all in Promise.all(areaPromises) shows as javaScriptDeprecated. .all is not deprecated in JS.

https://gist.github.com/3027255

Of course, it might be my coding that is at fault, but for some reason after a certain point it just makes EVERYTHING indented at the same level.

I've spent like an hour massaging where semicolons are, parens, and brackets, in an attempt to get the auto-indentation back (it was working perfectly till just a little while ago), but to no avail.

Putting /* in a single-quote string causes indentation issues. Double-quote strings don't have this problem. The problem doesn't arise if the /* is preceded by a / (so it's //*).

Here's an example of the problem.

There is something wrong with following statements in javascript file, like this:

var url = 'http://www.google.com/';

'.google.com' is highlighted.

Note the parenthesis from define method and around foo parameter.

Apparently it's related to the function keyword. See below examples:

Code folding is supported for normal function definition syntax

function test() {

}

But code folding is not supported for the alternate function definition syntax

    test: function() {

    }

Would it be possible to add support for the second syntax style as well?

Creating a colour-scheme for your very in-depth syntax, really appreciate it. What I do miss is special syntax on arrow notation.

let foo = (key) => {};

In the above, => is coloured due to being operators (unless I'm mistaken), whereas key does not get the argument colouring that is defined under javaScriptFuncArg.

#!/usr/bin/env node         
"use strict";               
module.exports = {          
  "a": function() {         

  },                        
  "b": function() {         

  },                        

};                          

When you enter a new entry, it adds an extra indent.

Verified that if i disable the plugin the indentation starts working normally again in this situation.

Also curious is that it requires two such functions, typing the "b" item does not cause erroneous indentation to occur. Note also the keys do not need to be in quotes to reproduce.

Since PHP files can include JavaScript blocks, it seems that this plugin gets invoked for PHP files as well. This plugin runs setlocal iskeyword+=$, which is a good thing for JavaScript; however, in PHP, including $ in 'iskeyword' breaks the expected behaviour of the word text object, as well as things like * and #. In PHP, class members are declared like public $foo, but accessed like $this->foo, so technically $ is not part of the variable name, but more of a variable indicator.

I know this plugin is for JavaScript, but it's nice not to have unexpected side effects. I can't think of a perfect solution to this, unfortunately.

In the YUIDoc specs it says that @param can be followed by two keywords: name of param and type of param (order actually doesn't matter).

Currently the syntax file only highlights the first word after @param.

It's still some error about ')', this is my codes:

var http = require("http");
var url = require("url");

function start(route, handle) {

function onRequet(request, response) {
    var postData = "";
    var pathname = url.parse(request.url).pathname;
    var query = url.parse(request.url).query;
    console.log("Request for "+pathname+" received.");
    //console.log("Request query for "+query+" received.");

    request.setEncoding("utf8");

    //request.addListener("data", function(postDataChunk) {
        //postData += postDataChunk;
        //console.log("Received POST data chunk '"+
            //postDataChunk + "'.");
    // });
    var db = {
        users: [
        {name: 'tobi'},
        {name: 'loki'},
        {name: 'jane'}
        ]
    };

    console.log(db.users['tobi']);


    request.addListener("end", function() {
        route(handle, pathname, response, postData);
    });

    route(handle, pathname, response);

    response.writeHead(200, {"Contest-Type": "text/plain"});
    response.write("Hello World!!!");
    //response.write(content);
    response.end();
}

http.createServer(onRequet).listen(8888);

console.log("Server has started.");

}

exports.start = start;

You can see the part about line 19:
" // });"
");" is not comment, it's a bug

How to reproduce:
Go to cursor object key than named as a url, error, title , href, target, ...
Go to command mode :echo map(synstack(line('.'), col('.')), 'synIDattr(v:val, "name")')
result: javaScriptHtmlElemProperties or javascriptDomElemAttrs, or javaScriptFetchAPIProperties ...

Indentation breaks when using 2 spaces for indentation.

To reproduce, first set this options:
:set tabstop=2 | set shiftwidth=2 | set softtabstop=2 | set expandtab

Then try this code and you should see that is indented as follows:

var foo = bar({
  a: 0,
    b:1
});

Setting indentation to 4 spaces fixes this.

After a backtick string interpolation the highlighthing breaks (line 12).

Screenshot with w0ng/vim-hybrid colors scheme.

The new keyword does not seem to be highlighted. I've tried several colorschemes and it still doesn't work.

Any reason because javaScriptLabel is commented out?

" syntax match javaScriptLabel ...

Well, the problem is clearly seen from the screenshots below.

I couldn't find any strict recomentation for JS to break the line after the closing brace. JSHint doesn't generate any warnings too.

All JS engines (as far as I know; tested in V8, SpiderMonkey, and JSC) support backslash-escaped multiline strings, but this still chokes on them. Really hoping for support, as it's hard to edit userscripts when your inlined CSS blows everything up.

Example of syntax:

var things = "this is a\
really long\
multiline string";

var foo = '<@m.message "someId">';

In this case I would expect everything within single quotes to be treated as a string, but message is shown with a different color and tagged as Special.

I think the origin plugin from Yi Zhao works with fold. But now, the function for folding code disappear.
Will u add it back ?

I've just recently started using ES6 syntax and template literals are breaking syntax highlighting for the rest of file when I have the following line in my .vimrc
au FileType javascript call JavaScriptFold()

Disabling folding removes the problem.

When folding is enabled:

When folding is disabled:

Hi there,

Thanks for your work.
Would it be possible with Vim's syntax matching to highlight usages of a function's arguments? For example, to highlight usages (of accommodationId, startDate, endDate and userId) in a function like below:

  ...
  requestAvailability: function(accommodationId, startDate, endDate, userId) {
    var deferred = Q.defer();
    var request = {
      deferred: deferred,
      userId: userId,
      accommodationId: accommodationId,
      startDate: startDate,
      endDate: endDate
    };
    if (!userId) {
      UserService.getLoggedInUser().then(function(data) {
        request.userId = data.user.id;
        _makeOrDelayAvailabilityRequest(request);
      });
      return deferred.promise;
    }
    _makeOrDelayAvailabilityRequest(request);
    return deferred.promise;
  }
  ...

I see this in just about all syntax files, but it really doesn't make any sense when you think about it.

Why do we highlight the actual 'function' keyword. Who gives a shit?

HiLink javaScriptFuncKeyword Function

Instead, why not highlight the function's name and identifier, which is far more likely to be the important bit that needs to stand out, not the literal word 'function'?

As far as I'm concerned it should be:

HiLink javaScriptFuncKeyword Noise

Thoughts?

Not sure if this is related to solarized or not, but when you create plain object properties that happen to also be DOM element properties, they're colored as such, which seems inconsistent. See tagName and className in the screenshot below.

I apologize for the dumb question but what is the syntax group for a general variable name?
I want something like let myVar = 5; to have coloring on the myVar.

I use youcompleteme , and installed this plugin, but it does not work as your example

I installed this plugin using Pathogen as per instruction:

git clone https://github.com/jelera/vim-javascript-syntax.git ~/.vim/bundle/vim-javascript-syntax

Then included the following in my .virc file

au FileType javascript call JavaScriptFold()

After restarting vim and opening a JavaScript file I am not able to fold using the standard zo, zc commands .. any clue ?

same as #56 but more description,

I have the same issue, using
[email protected]:luochen1990/rainbow.git plugin at current latest hash: 18b7bc1 is:
to replicate I have a new file with a content:
[].map(function(a,b){ })
you will see the parenthesis has shifted color right after "b",
everything inside the curly braces is fine, except if you have another
function passed as a parameter

Hi jelera, I found a strange behavior.
If my code like below:

function test() {
  // {}
  var val1;
}

The fold for the function will be wrong. You could reproduce it.

E.g.

var device;

var device; // this is a device

It is not necessary that there be something following the space (as in the example with the comment).