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

[REQUEST] Support YAML config alongside rasi #1884

Closed
2 tasks done
EmilyGraceSeville7cf opened this issue Aug 6, 2023 · 5 comments
Closed
2 tasks done

[REQUEST] Support YAML config alongside rasi #1884

EmilyGraceSeville7cf opened this issue Aug 6, 2023 · 5 comments

Comments

@EmilyGraceSeville7cf
Copy link

EmilyGraceSeville7cf commented Aug 6, 2023

Before opening a feature request

  • I checked the next branch to see if the feature has already been implemented
  • I searched existing reports to see if it is already requested.

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.

@EmilyGraceSeville7cf
Copy link
Author

Another possible solution of issue not having config linting is to implement LSP for .rasi. But I can't do it right now, unfortunately.

@DaveDavenport
Copy link
Collaborator

I have no plans for changing the config file or supporting multiple parsers.

As a sidenote, there is already application launcher (at least one) configured in YAML.

Great, so there is a solution for you.

@DaveDavenport DaveDavenport closed this as not planned Won't fix, can't repro, duplicate, stale Aug 6, 2023
@DaveDavenport
Copy link
Collaborator

On a side note, yaml can be terrible to work with. While I don't have time go into details, this
https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-from-hell explains some of the issues I've ran into.

@EmilyGraceSeville7cf
Copy link
Author

Thanks for the article. ;)

@github-actions
Copy link

github-actions bot commented Sep 7, 2023

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants