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

VS Code extension: no autocompletion for variant groups or their prefixes #2619

Open
4 tasks done
PhilippMolitor opened this issue May 14, 2023 · 5 comments · May be fixed by #3877
Open
4 tasks done

VS Code extension: no autocompletion for variant groups or their prefixes #2619

PhilippMolitor opened this issue May 14, 2023 · 5 comments · May be fixed by #3877

Comments

@PhilippMolitor
Copy link

UnoCSS version

0.15.12, vs code: 0.51.12

Describe the bug

When using variant groups, autocomplete does not work inside parentheses:
image
(ignore the error, this is eslint complaining about the order or classes)

Also, the autocompletion for variant prefixes themselves (likehover:) does not work.

Also see: #1768

Reproduction

Use the current VS Code Plugin and variant groups.

System Info

No response

Validations

@stale
Copy link

stale bot commented Jul 13, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Jul 13, 2023
@PhilippMolitor
Copy link
Author

still no reply from the author

@stale stale bot removed the stale label Jul 13, 2023
@stale
Copy link

stale bot commented Sep 12, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Sep 12, 2023
@stale stale bot closed this as completed Sep 19, 2023
@Dav3rs
Copy link

Dav3rs commented Mar 14, 2024

This issue remains unresolved, please no-stale.

@antfu
Copy link
Member

antfu commented Apr 5, 2024

It's a known limitation. Due to the complexity it involves, the ROI does not seem ideal. Open for PRs if there would be a clean solution to that, otherwise I don't expect it to be supported any sooner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants