Smarter JavaScript completion in IntelliJ IDEA 11.1

This is a cross-post from WebStorm & PhpStorm blog, originally posted by Konstantin Ulitin.

We are getting a lot of reports and ideas from you about the ordering of JavaScript completion options. So in IntelliJ IDEA we made small but important improvements. More relevant suggestions now appear at the top of the list in many cases.

1. Suggested names are ordered by their definition scope nesting, i.e. global variables are placed at the bottom of the list.

2. Object members are ordered by class inheritance.

3. If a local variable exists with the same name as the parameter of the called function, that variable is considered the most relevant.

All these rules also apply to ActionScript completion.

You can explore these features in IntelliJ IDEA 11.1. Your comments and suggestions are welcome in our issue tracker

About Andrey Cheptsov

Andrey Cheptsov is IntelliJ IDEA product marketing manager at JetBrains. He's passionate about productivity, programming languages and tools.
This entry was posted in New Features and tagged , . Bookmark the permalink.

4 Responses to Smarter JavaScript completion in IntelliJ IDEA 11.1

  1. Arikon says:

    How the class inheritance is guessed?

  2. John D. says:

    Nice, but IDEA 11.1 is much slower and consumes more resources than IDEA 10 on WindowsXP :( .
    (even if the opposite is stated in the “new features” of the product description).

  3. yole says:

    John,
    Please capture a CPU snapshot as described in http://devnet.jetbrains.net/docs/DOC-192 and file an issue with the snapshot attached.

  4. Konstantin Ulitin says:

    Arikon,
    For JavaScript this works for prototype inheritance, and some frameworks mechanisms of class inheritance (as ExtJS in example).

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>