[wp-trac] [WordPress Trac] #33021: Global javascript variables incorrectly defined

[WordPress Trac]

#33021: Global javascript variables incorrectly defined
------------------------------+-------------------------
 Reporter:  johnjamesjacoby   |       Owner:  nacin
     Type:  defect (bug)      |      Status:  closed
 Priority:  normal            |   Milestone:  4.3
Component:  Build/Test Tools  |     Version:
 Severity:  normal            |  Resolution:  fixed
 Keywords:  has-patch         |     Focuses:  javascript
------------------------------+-------------------------

Comment (by nacin):

 Replying to [comment:9 johnjamesjacoby]:
 > Jorbin/Nacin:
 > * Do either of you use PHPStorm or Netbeans?
 > * If so, have you configured this to better comprehend the benefits?
 > * If not, in the future can we delegate decisions like these to someone
 who can speak to the importance of their effectiveness before threatening
 to close the next ticket(s) that come in?

 Great questions. I suspect @jorbin just misunderstood the significance of
 `global` versus `globals`. It's confusing — I even had to submit a bug
 report, because the JSHint website is confused too! Beyond that, the
 `.jshintrc` file absolutely needs to be read by the IDE for any JSHint
 integration to be useful, so it made total sense to mark this ticket for
 closure. As your links indicated, both PHPStorm and Netbeans read from
 `.jshintrc`, so there you go. I am not sure if you think there are
 additional benefits here that deserve an additional commit?

 I have used PHPStorm in the past, and I just finished managing a project
 to integrate JSHint into a project with more JavaScript than WordPress;
 it's a Java project and thus this involved JSHint + Eclipse. So yeah, some
 experience here.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/33021#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform