Very useful. Being able to set collapse to definitions when opening a JS file means I don't have to search for another extension that does this. Thanks. --Mike
Syntax highlight doesn't seem to work for .js files
I get everything black, except string literals which are blue
Functions are folding OK
region does not fold.
I have disabled all other extensions
This is strange because JSE should not affect highlighting. Do you have this issue on all js files or just some of them? If you disable JSE, does it get fixed?
Hi,
This is a great extension I should first say. Was just curious that since Web Essentials extensions has also come out with what looks like similar features (plus other stuff) can you comment on whether you think there is a bit of overlap between the two (maybe you two could somehow collaborate together to use the best of both?)
Thanks!
Hey! You've done a great work indeed!
One issue to improve:
I checked the Collapse to definitions option.
When the js is wrapped in IIFE, inner methods are not collapsed. F.x. one() is not collapsed, but the top level anonymous fx is.
(function($){
function one(){
....
}
})(jQuery)
Thanks for the extension I think it is a big help in organizing JavaScript files. When I installed the extension yesterday expanding/collapsing of functions and regions worked fine. For some reason though the expand/collapse node for region is only showing up after a file has been edited. This problem doesn't happen with functions.
Hi
I suppose it'a conflict with another extension. Do you have any other extensions installed, especially those with similar functionality? Does this issue appear if you disable all other extensions?
I don't have any other extensions installed. What's happening is that a few seconds after I put a line break after the start of //#region the expand/collapse node shows up. I thought that TFS might somehow be having an impact on this so I started a new website not under source control and found that the same thing is happening.
Good work here. I have tried your extension, and read the comments below. However, one little bug bear I have with visual studio editor, (and I have read many like it), is that it can’t collapse directly at the { under a c# method. Instead favouring to collapse at the method name.
The issue I have with this is that C# allows you technically to use { } anywhere. So if you could collapse at the { you would then be able to put them around stuff like case statements and even collapse long loops or conditionals. Or just encase a piece of code you want to get out of the way in a set of { } and collapse it.
Since you are developing this tool for Java script and CSS, perhaps you can shed some insight on how to add the feature above to the C# environment.
Another reason I like using the idea of { to collapse code between { } is because it is one character long to begin, and one character long to end. As opposed to the equivalent #region name, and #end region name which serves no other purpose than to do what I am requesting but looks like a precompiler directive in C++. Personally I don’t really like the look of it and I’m too lazy to type at least 17 characters and a name when I can get away with 2 and a name.
Anyway, your insight on this would be welcome, and also any ideas you may have to help overcome it, I assume it is an advanced problem considering so many programmers are looking for a solution and nobody has come up with one yet.
Thanks for your input.
Regards
Hi
A friend fo mine already adapted this extension to C#. It's called C# outline (http://visualstudiogallery.msdn.microsoft.com/4d7e74d7-3d71-4ee5-9ac8-04b76e411ea8)
Unfortunately, I couldn't reproduce this bug. Created the file and nothing happened.
I need this file exactly as you created it. Maybe there is something about encoding or special symbols. You can send it to ryder86@gmail.com. You can also send reset.css, base.css and fonts.css, they may be important too.