Use of a < with no whitespace near it results in weird colors about babel-sublime HOT 6 CLOSED

Yeah, I've known about this but I don't think there's a solution. Sublime can't match across new lines, but a single JSX tag can run multiple lines - in fact, it's a very common pattern:

<div className='PanelSearch'>
  Search<input
    className='PanelSearch-field'
   /* comments */
    onChange={this.onInputChangeHandler}
    onKeyDown={this.onInputKeyDownHandler}
    value={props.query}
  />
</div>

So we only match the opening part of the tag (e.g.: <Tag) then try to match attributes and comments, since those can be on another line.

from babel-sublime.

Are semicolons allowed inside JSX tags? If not, maybe that can be a heuristic to differentiate JSX tags from comparison operator.

from babel-sublime.

@dashed good call! Can you and @hawkrives give #33 a test drive before I merge it?

from babel-sublime.

@hawkrives I just pushed the fix for this issue in v2.0.0 - should be picked up by Package Control within the hour.

from babel-sublime.

Excellent. Sorry I didn't get around to testing this— today was a bit hectic. 

I'll see if I spot anything!

On Sat, Feb 14, 2015 at 10:28 PM, Andres Suarez [email protected]
wrote:

@hawkrives I just pushed the fix for this issue in v2.0.0 - should be picked up by Package Control within the hour.

Reply to this email directly or view it on GitHub:
#29 (comment)

from babel-sublime.

no worries!

from babel-sublime.