ReSharper Javascript Intellisense: Too many options

I have downloaded version 6 of ReSharper and am playing with its javascript support.  My first impressions are that while it is promising, it seems that on a large website, the number of options in the intellisense drop down are so many that it makes it close to useless.  Visual Studio's built in intellisense relies on special ///<reference path="" /> elements at the top of the .js file to figure out what the dependencies of a .js file are, and that helps keep its intellisense options at a managable number.  Is there any thought to supporting this in ReSharper's javascript intellisense?  I like the <reference /> approach for two reasons, it helps document your dependencies for your script (very useful in a non-trivially sized web application), and it keeps the intellisense from becoming so noisy to where it is almost unusable.

10 comments

Further to the point about too much stuff in JS completion lists (not sure what my general view on that is), I am seeing R# offer JS completions based on JS files that are in other projects within the solution.

For example, in a project which uses only jQuery 1.5.1, I am also being offered completions from jQuery 1.3.2, which is used by a different project within the same solution (at least, I assume that's where it's getting it from).   I know JS completion is always going to be a bit hit-or-miss, but I don't think it's appropriate to search a different project for completion possibilities.

Is this is a known bug?

0

I agree with this concern.

I can't think of any way for Resharper to know for sure which .JS files will
be active at runtime.

I've listed the ones I want at the top of the JS file using  approach for two reasons, it helps document your
dependencies for your script (very useful in a non-trivially sized web
application), and it keeps the intellisense from becoming so noisy to where
it is almost unusable.

---
Original message URL: http://devnet.jetbrains.net/message/5291165#5291165

0

I'm actually finding that some of the (very wrong) intellisense is
apparently coming from a file called "dhtml.js" which is nowhere to be found
in my solution or anywhere on my computer (that I can find)!

Build 6.0.2102.59

Glen


"Glen Little"  wrote in message
news:ikjn6u$iqu$1@nntp-server.labs.intellij.net...

I agree with this concern.

I can't think of any way for Resharper to know for sure which .JS files will
be active at runtime.

I've listed the ones I want at the top of the JS file using  approach for two reasons, it helps document your
dependencies for your script (very useful in a non-trivially sized web
application), and it keeps the intellisense from becoming so noisy to where
it is almost unusable.

---
Original message URL: http://devnet.jetbrains.net/message/5291165#5291165

0

There seem to be various 'pseudo-js-files' which attempt to provide suggestions for stuff which is expected to be present but is not going to explicitly appear in in a project's own files.   These files are all resources in JetBrains.ReSharper.Psi.JavaScript.dll if you want to see what's in them.

Interestingly enough, there's even a jQuery one - I guess there will be some provision made for overriding that with a more relevant version or .vsdoc file if you have one in the project.  It is obviously one source of the half-dozen semi-duplicate jQuery suggestions I get in the js editor.

0

Hello Andrew,

We're planning to support /// for javascript in IntelliSense
in ReSharper 6.0, although it hasn't been added yet. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I have downloaded version 6 of ReSharper and am playing with its
javascript support.  My first impressions are that while it is
promising, it seems that on a large website, the number of options in
the intellisense drop down are so many that it makes it close to
useless.  Visual Studio's built in intellisense relies on special
///<reference path="" /> elements at the top of the .js file to figure
out what the dependencies of a .js file are, and that helps keep its
intellisense options at a managable number.  Is there any thought to
supporting this in ReSharper's javascript intellisense?  I like the
<reference /> approach for two reasons, it helps document your
dependencies for your script (very useful in a non-trivially sized web
application), and it keeps the intellisense from becoming so noisy to
where it is almost unusable.

---
Original message URL:
http://devnet.jetbrains.net/message/5291165#5291165



0

Hello Glen,

Could you please elaborate more on this problem? Which items coming from
dhtml.js do you consider wrong and why? Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

I'm actually finding that some of the (very wrong) intellisense is
apparently coming from a file called "dhtml.js" which is nowhere to be
found in my solution or anywhere on my computer (that I can find)!

Build 6.0.2102.59

Glen

"Glen Little"  wrote in message
news:ikjn6u$iqu$1@nntp-server.labs.intellij.net...

I agree with this concern.

I can't think of any way for Resharper to know for sure which .JS
files will be active at runtime.

I've listed the ones I want at the top of the JS file using
<reference/>. However, the intellisense is not using that information,
and instead, showing me tips from numerous files that will NOT be
available at runtime.

Glen

"Andrew Alm"  wrote in message
news:23308048.9791298926012647.JavaMail.devnet@domU-12-31-39-18-36-57.
compute-1.internal...
I have downloaded version 6 of ReSharper and am playing with its
javascript support.  My first impressions are that while it is
promising, it seems that on a large website, the number of options in
the intellisense drop down are so many that it makes it close to
useless.  Visual Studio's built in intellisense relies on special
///<reference path="" /> elements at the top of the .js file to figure
out what the dependencies of a .js file are, and that helps keep its
intellisense options at a managable number.  Is there any thought to
supporting this in ReSharper's javascript intellisense?  I like the
<reference /> approach for two reasons, it helps document your
dependencies for your script (very useful in a non-trivially sized web
application), and it keeps the intellisense from becoming so noisy to
where it is almost unusable.

---
Original message URL:
http://devnet.jetbrains.net/message/5291165#5291165



0

Hi,

It would be nice also to have something like - missing "using"s detection for javascript files as well. Might be especially helpful when R# will have '///' support.

BTW, if it's possible, could you post a list of JS-related major features expected in 6.0? So that it will be possible to track and explore them when they're done?


Regards,
Sergei

0

Just a note - I'm currently testing your WebStorm IDE and I would REALLY like see similar functionality in Visual Studio with ReSharper. I'm not sure, if it is feasible, because the WebStorm offers lot of other goodies not present in Visual Studio, like change tracking, great "search" feature and others. The fact is I would really like to use only one IDE with great JavaScript support for developing web sites with jQuery and stuff, than using two IDEs at a time with different keyboard shorcuts, buttons...

0

Hi. We've come up with a list of planned(green in the list)/implemented features. Currently it only contains summary on the most of the features but I plan to supplement it with details. http://checkvist.com/checklists/61507-javascript-features

0

Thanks!

Now it's much more easy to see where resharper is headed.

P.S. I couldnt help but notice the weird time you posted your reply.

0

Please sign in to leave a comment.