"The prop value with an expression type of AssignmentExpression could not be resolved." about jsx-ast-utils HOT 6 CLOSED

Absolutely yes. The throw - and the logging - are just the feedback mechanism for how we do that.

That makes sense. I hadn't thought about it that way. Thanks for reopening them.

from jsx-ast-utils.

Oy- will get this added in as soon as possible, thanks for reporting 😄

from jsx-ast-utils.

@notatestuser , Fixed in version v2.2.1. This will log an error in the console, but it will no longer throw.

from jsx-ast-utils.

@ljharb are you thinking that jsx-ast-utils should proactively account for these node types?

from jsx-ast-utils.

Absolutely yes. The throw - and the logging - are just the feedback mechanism for how we do that.

from jsx-ast-utils.

Also happens with +=, e.g.:

let bar = 0;
<div foo={bar += 1} />

I found something like this in our codebase that was causing this message. It turned out to be a minor bug (was supposed to be +).

Would it be possible to display the file/line where the error happened when this error is logged?

from jsx-ast-utils.