Skip to content

v4: Show completions after any valid variant #1263

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

Merged
merged 5 commits into from
Mar 19, 2025

Conversation

thecrypticace
Copy link
Contributor

@thecrypticace thecrypticace commented Mar 14, 2025

Fixes #943
Fixes #1257

This doesn't ensure variants like not-supports-* are suggested because not-supports: isn't valid. Only something with a value is e.g. not-supports-display. Making that work (it really should) is a larger task and requires designing an interactive suggestion API for v4.

@thecrypticace thecrypticace force-pushed the fix/completions-after-arbitrary-variants branch 2 times, most recently from b148c18 to 06df6d5 Compare March 14, 2025 20:21
@thecrypticace thecrypticace marked this pull request as ready for review March 18, 2025 17:00
@thecrypticace thecrypticace force-pushed the fix/completions-after-arbitrary-variants branch from f086f81 to 63c0f68 Compare March 18, 2025 17:05
This was just dead code b/c the version number is not 2.x
We weren’t handling the case of arbitrary variants, variants with an arbitrary value, and variants with bare values. We have to compile a dummy class temporarily to determine whether or not the class is valid
@thecrypticace thecrypticace force-pushed the fix/completions-after-arbitrary-variants branch from 63c0f68 to c660b19 Compare March 19, 2025 13:59
@thecrypticace thecrypticace merged commit 0d9bd2e into main Mar 19, 2025
@thecrypticace thecrypticace deleted the fix/completions-after-arbitrary-variants branch March 19, 2025 14:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants