Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should vat select JSX tags? #2431

Closed
skube opened this issue Mar 8, 2018 · 3 comments
Closed

Should vat select JSX tags? #2431

skube opened this issue Mar 8, 2018 · 3 comments
Labels
status/already-resolved Fixed in previous version

Comments

@skube
Copy link

skube commented Mar 8, 2018

BUG REPORT:

What happened:
Using JSX with custom Components and using vit or vat, custom JSX tags are ignored.

What did you expect to happen:
I expect custom JSX html-like tag to be selected

How to reproduce it (as minimally and precisely as possible):

<div>
  <MyCustomComponent>
    |
  </MyCustomComponent>
</div>

If cursor is at pipe (|), then hitting vatselects the outer div and seems to ignore the <MyCustomComponent> tag.

Environment:

  • Extension (VsCodeVim) version: 0.11.1
  • VSCode version: 1.21.0
  • OS version: 10.13.3
@Chillee
Copy link
Member

Chillee commented Mar 8, 2018

Could you provide a repro file? I can't reproduce this on a new file.

@skube
Copy link
Author

skube commented Mar 9, 2018

Actually, I've isolated the issue. It's when the prop contains an element that vim gets confused.

<div>
  <Component
    prop={<div>lorem</div>}
  >
    | 
  </Component
</div>

@xmbhasin
Copy link
Contributor

xmbhasin commented Oct 11, 2018

I believe this was fixed in #2921. The second example provided is missing a > in the second Component tag, after fixing that, vat seems to work as expected.

@skube skube closed this as completed Feb 4, 2022
@J-Fields J-Fields added the status/already-resolved Fixed in previous version label Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/already-resolved Fixed in previous version
Projects
None yet
Development

No branches or pull requests

4 participants