-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feat: improve completion items #10
Comments
I think the full name is a good choice. But I would rather prioritize for the shorter namespace, and not proposing the childrens. The idea is to achieve a flow of multiple autocompletion by narrowing the context. I find myself trying to do that with the extension, but it's not supported for now. Here is an example :
Presently, the behavior in bold are not implemented, but I think it would benefit greatly to the DX. The second improvement would be to prioritize child rules of the current namespace, and then the parents' one. And not autocomplete from the root when a rule is found, instead just having the relative path from the common ancestor. |
It would be great for sure! However, I'm not sure that's possible as spaces are allowed in rule names 🤔 |
Mmmh, good point. It could be done so that when the selected autocompleted rule has children (is a namespace), the inserted string automatically adds a trailing Or maybe I'm missing a technical limitation of some other kind? |
As the rule names are often really long, it's difficult to choose the right item from the completion menu:
We need to find a way to make it more readable. Here a few ideas (don't hesitate to suggest others @johangirod @Clemog):
logement . électricité . photovoltaique . présent
becomeslog . éle . pho . présent
)The text was updated successfully, but these errors were encountered: