-
Notifications
You must be signed in to change notification settings - Fork 608
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
[REQUEST] Support YAML config alongside rasi #1884
Comments
Another possible solution of issue not having config linting is to implement LSP for .rasi. But I can't do it right now, unfortunately. |
I have no plans for changing the config file or supporting multiple parsers.
Great, so there is a solution for you. |
On a side note, yaml can be terrible to work with. While I don't have time go into details, this |
Thanks for the article. ;) |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Before opening a feature request
What is the user problem or growth opportunity you want to see solved?
There is no IntelliSence (link to extension) in VS Code for .rasi files, just syntax highlighting. So it's not very convenient to write .rasi files without any assistance.
How do you know that this problem exists today? Why is this important?
There is no JSON schema available for rofi neither in SchemaStore nor here. Also, AFAIS there is no YAML config support for now.
Who will benefit from it?
Users who use YAML Red Hat extension in VS Code or similar extensions in other editors which provide IntelliSence based on JSON schema.
Rofi version (rofi -v)
1.7.1
Configuration
default settings
Additional information
I can write JSON schemas, so this is one of the reasons I'm suggesting this feature to be implemented. I can design YAML schema and provide YAML config examples I would like to see.
As a sidenote, there is already application launcher (at least one) configured in YAML.
The text was updated successfully, but these errors were encountered: