-
-
Notifications
You must be signed in to change notification settings - Fork 389
More plugin introspection information #3660
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
Comments
This would help the user in e.g. #3618 to know what's going on. |
It would also be nice to know whether a plugin is enabled or not. We could imagine having something like:
Then |
I think that this could let us push much more conditional logic into the plugin packages, which might be nice. For example, we could have something like this in
and then in
Then in the main HLS executable we can unconditionally depend on the stylish-haskell plugin, and we'll either get the real plugin or a placeholder "disabled" plugin, depending. |
Thinking a bit, what information should have for a specific plugin? Besides And other plugins seems don't have any words to say... |
Brainstorming:
Some of this we already know, but might need more annotation in order to let us show it to the user in a readable way. |
Before making a decision here, should we add a log while formatters are activated to describe its version? |
At the moment we know a little bit about plugins, but mostly their names. It would be nice if plugins could provide us with some extra information: a description, perhaps some optional version information about what key libraries it was built against (e.g. ormolu).
We could then at least log this information when we startup.
The text was updated successfully, but these errors were encountered: