-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
JSX/HTML tag auto-close feature #5267
Comments
+1 This is something so standard that it's even strange to program it without auto-closing tags I hope they improve this because it helps a lot with the developer experience Thanks for u work Zed team ! |
Astro support was added recently 🎉 and would also greatly benefit from auto closing tags |
this is the only reason why i didn't 100% switch to zed , when will this come ? or is it already possible yet? |
This would also be good in .vue files |
We need this please, it makes the developer experience so smooth. It feels weird not having it. |
Yes, i agree this is important for anyone doing web development. i'll wait a bit until it's there, or i'll look into fixing it myself. |
It would help a lot with productivity, I think it’s very important |
is there any progress here? this small feature will make my life so much easier |
I'm going to repost what I've already said on Twitter for the sake of transparency:
|
This is the main reason I have not switched to Zed fully yet |
Fixes #5267 TODO: - [x] Publish our fork of vscode-langservers-extracted on GH and wire that through as a language server of choice for HTML extension. - [x] Figure out how to prevent edits made by remote participants from moving the cursor of a host. Release Notes: - Added support for autoclosing of HTML tags in local projects.
For some reason, this feature doesn't really work on Zed Preview 0.137.0. |
Does not work in jsx/tsx |
Only HTML support has just landed. Be sure to +👍 this other issue for JSX / TSX support. |
Should it be working in TSX files? |
I think it should for react based files/projects |
it's not working on jsx/tsx Nextjs project app router typescript |
it's not working too with blade.php will be waiting on this 👍🏾 |
Also does not work for .heex files. |
It does not work with .vue files |
it dose not work with .svelte file |
.astro not working |
Please fix supporting for TSX/JSX so I can fully migrate from VSCode to Zed |
same here |
Please implement this, not having it practically leaves out every front end developer. |
I have given up on Zed because of this The team seems more interested in AI and adding vim features than "minor issues" like these The fact that basic stuff like formatting in snippets, tag autorename / auto close, is not working for months with 0 word to even give users hope is just disheartening It's a great editor, but if you can't get even the most essentials to work, then what's the point |
is not working in tsx 🥺 |
add suport to jsx 🙏 |
Within ./zed/snippets/tsx.json you can define custom snippets. For example, configuring a snippet such that typing div expands into paired
|
Well this definitely helps, but it only solves half the problem.. what of custom tags? What of none self-closing components, having to create snippets but every possible use case won't cut it |
Thank you for sharing this! However, this is still quite far from solving the problem. If we have a table or any other tags, should we really make this a lengthy configuration? Or what if we had components? |
install the emmet extention it works fine for me on tsx and jsx files |
@3ux1n3 omg, thanks, that actually works!! |
Check for existing issues
Is your feature request related to a problem?
It's a bit frustrating to add the close tag at the end of the
jsx
element orhtml
element. So, having that auto-close tag functionality will definitely help there.Describe the solution you'd like
Something like the
vscode
setting for auto-close tag feature. As soon as you type the opening of the tag, the end of the tag comes as well.If applicable, add mockups / screenshots to help present your vision of the feature
No response
The text was updated successfully, but these errors were encountered: