Doesn't handle lambda functions about vim-jsx HOT 11 CLOSED

@toroman—User error? Works fine for me; you most likely haven't installed vim-javascript, or have another plugin that's introducing a disruptive conflict.

from vim-jsx.

Huhn... I've never seen this lambda syntax. Is it an ES6 thing?

from vim-jsx.

I have vim-javascript, not sure if something else is messing it up.

On Mon, Feb 1, 2016 at 11:12 AM, Max Wang [email protected] wrote:

@toroman https://github.com/toroman—User error? Works fine for me; you
most likely haven't installed vim-javascript, or have another plugin that's
introducing a disruptive conflict.

—
Reply to this email directly or view it on GitHub
#66 (comment).

~toroman

from vim-jsx.

Fact is, disabling vim-jsx solves the problem.

On Mon, Feb 1, 2016 at 11:38 AM, Srecko Toroman [email protected]
wrote:

I have vim-javascript, not sure if something else is messing it up.

On Mon, Feb 1, 2016 at 11:12 AM, Max Wang [email protected]
wrote:

@toroman https://github.com/toroman—User error? Works fine for me; you
most likely haven't installed vim-javascript, or have another plugin that's
introducing a disruptive conflict.

—
Reply to this email directly or view it on GitHub
#66 (comment).

~toroman

~toroman

from vim-jsx.

I'd expect that disabling vim-jsx also makes inline XML highlighting break...

Anyway, I've tested some more lambda-syntax cases, and they all seem to work. This is probably due to an outdated vim-javascript package, or some other package that interferes. (There are some auxiliary JS packages that don't do filetype detection correctly for compound filetypes, e.g.) In any case, it's not a vim-jsx issue.

(And I would—but I work out of Boston now :D)

from vim-jsx.

This is a little bit of a separate comment, but while the fat-arrow syntax has been added to es6 (see babel's docs), but it in't a good idea to use bind(this) or arrow functions in the props the way this request is asking to do things. See the description of the eslint-plugin-react rule "jsx-no-bind: Prevent usage of .bind() and arrow functions in JSX props" for details (https://github.com/yannickcr/eslint-plugin-react/blob/master/docs/rules/jsx-no-bind.md).

from vim-jsx.

@toroman—Can you screenshot the example? Is the problem that the => is closing the tag, perhaps?

from vim-jsx.

I actually can't repro this anymore (I don't remember if I tried before...). Is it still an issue for you, @toroman?

from vim-jsx.

No I don't think so. I actually disabled the extension because it messes up
the indentation. Like, new lines always start at column 0. Very annoying.
Not sure what's causing it.

On Mon, Feb 1, 2016 at 9:37 AM, Max Wang [email protected] wrote:

I actually can't repro this anymore (I don't remember if I tried
before...). Is it still an issue for you, @toroman
https://github.com/toroman?

—
Reply to this email directly or view it on GitHub
#66 (comment).

~toroman

from vim-jsx.

So let me know if you want to stop by my desk and investigate :)

On Mon, Feb 1, 2016 at 11:38 AM, Srecko Toroman [email protected]
wrote:

Fact is, disabling vim-jsx solves the problem.

On Mon, Feb 1, 2016 at 11:38 AM, Srecko Toroman [email protected]
wrote:

I have vim-javascript, not sure if something else is messing it up.

On Mon, Feb 1, 2016 at 11:12 AM, Max Wang [email protected]
wrote:

@toroman https://github.com/toroman—User error? Works fine for me;
you most likely haven't installed vim-javascript, or have another plugin
that's introducing a disruptive conflict.

—
Reply to this email directly or view it on GitHub
#66 (comment).

~toroman

~toroman

~toroman

from vim-jsx.

Ah, kk. Will update my plugins and check for conflicts.

Best,
Srecko

On Mon, Feb 1, 2016 at 11:51 AM, Max Wang [email protected] wrote:

I'd expect that disabling vim-jsx also makes inline XML highlighting
break...

Anyway, I've tested some more lambda-syntax cases, and they all seem to
work. This is probably due to an outdated vim-javascript package, or some
other package that interferes. (There are some auxiliary JS packages that
don't do filetype detection correctly for compound filetypes, e.g.) In any
case, it's not a vim-jsx issue.

(And I would—but I work out of Boston now :D)

—
Reply to this email directly or view it on GitHub
#66 (comment).

~toroman

from vim-jsx.