CODEWITHSUNDEEP
javascriptjshint
user656925
user656925

Reputation:

Why does jshint not recognize an assignment as an expression?

How do I need to modify these lines to make jshint happy?

An assignment is an expression. Why doesn't jshint understand this? Obviously the interpreter does.

Line 572: while(bookmark_element=bookmark_list[iterator++])

Expected a conditional expression and instead saw an assignment.


Line 582: while(bookmark_element=bookmark_list[iterator++])

Expected a conditional expression and instead saw an assignment.


Line 623: while(element_iterator=element_iterator.nextSibling)

Expected a conditional expression and instead saw an assignment.

Upvotes: 19

Views: 9174

Answers (8)

Ishan Patel
Ishan Patel

Reputation: 6091

Add /* jshint expr: true */ comment in your Javascript file, it will not show warning anymore.

Upvotes: 0

Erasmus Cedernaes
Erasmus Cedernaes

Reputation: 1915

There are at least two ways to solve the reported error, according to JSHint docs.

  1. Add /*jshint boss:true */ before conditional statement
  2. Wrap statement in extra parentheses, i.e. while ((element_iterator = element_iterator.nextSibling)) {...}

Personally, I think surrounding with extra parentheses is best practice since it keeps the error check but still makes good sense code-wise. Adding the !! before does actually nothing but convert the expression to true/false back and forth two extra times.

Upvotes: 4

Ben
Ben

Reputation: 57209

I had this error because I had a trailing comma in a declaration preceding the function:

this.foo = "bar",   // <- Error was here

this.myfunc = function() {
   ...   // <- Error reported on this line
};

(It was hard to find, but reinforces my opinion that linters are usually right, it's my code that's wrong. If I had disabled the warnings globally - or even in that spot - the bug still would have been present.</lecture>)

Upvotes: 0

Dave Newton
Dave Newton

Reputation: 160181

/*jshint boss:true */

Experiment with the options.

Upvotes: 19

Mark Byers
Mark Byers

Reputation: 837996

I'm sure that jshint understands the expression fine, it is just that most people who write if (a = b) actually meant if (a == b) and so this generates a warning.

Since your code is what you intended you could add an explicit test:

while ((element_iterator = element_iterator.nextSibling) !== null) { ... }

Upvotes: 13

sq33G
sq33G

Reputation: 3360

jshint can't tell if you really meant to make an assignment in the condition block, or if that was really supposed to be a comparison. The concern would be that other humans might have the same doubt.

In the case of an iterator, I think you're okay.

Upvotes: 0

Rob W
Rob W

Reputation: 348972

If you really want to listen to JSHint, convert the expression to a boolean by:

while (!!(bookmark_element=bookmark_list[iterator++]))

! means: Something that evaluates to true is converted to false,
         something that evaluates to false is converted to true.

So, !! means: Convert something to the conditional representation.

Upvotes: 20

Ry-
Ry-

Reputation: 224857

It is an expression, and you can modify it to work with JSHint (although it's not nice) like so:

while(element_iterator.nextSibling) {
    element_iterator = element_iterator.nextSibling;

For your last example. However, you don't need to do this. JSHint is only a tool to help you improve coding habits and correct mistakes, but given that what you have is clear, concise, and (in my opinion) the best way of doing it - just ignore those messages.

Upvotes: 0

Related Questions