9cd4517a64
The implementation was checking if the comment was inside of the expression range, which seems like a good idea. Unfortunately, the expression range is not what's inside of `${}` but the actual AST node, which incidentally doesn't include comments. So the logic was off and returned `undefined` which threw afterwards.
Another solution is to find the first quasi where start is > comment start. This means that the comment appeared between the quasi before and this one... therefore in the expression before!
The flow parser has issues with unicode where it makes node location invalid, there are likely other places where node locations are off. So instead of throwing with a weird error, let's attach it to the first one if it doesn't work.
Fixes #1293
|
||
|---|---|---|
| .. | ||
| comments.js | ||
| deprecated.js | ||
| doc-builders.js | ||
| doc-debug.js | ||
| doc-printer.js | ||
| doc-utils.js | ||
| fast-path.js | ||
| options.js | ||
| parser.js | ||
| printer.js | ||
| util.js | ||