-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
Add more features and demos in docs #2257
Conversation
jneira
commented
Oct 5, 2021
•
edited by gitpod-io
bot
Loading
edited by gitpod-io
bot
- Copied from https://github.com/haskell/vscode-haskell#features
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! In the long run I think it would be cool to have a page per plugin which explains their features, has demos etc, and then this could link out to all those? Otherwise in the long run I think it's going to be hard for us to keep track of all our features!
docs/features.md
Outdated
![Call Hierarchy in VSCode](https://github.com/haskell/haskell-language-server/raw/2857eeece0398e1cd4b2ffb6069b05c4d2308b39/plugins/hls-call-hierarchy-plugin/call-hierarchy-in-vscode.gif) | ||
|
||
|
||
## How to show local documentation on hover |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't seem like it belongs in a "features" list per se? It's more like "setup instructions to get this feature to work". I'm not sure where that belongs, perhaps in Configuration
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm yeah you are right, thanks for the suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done!
Yeah that is the plan outlined here: #2066, will update it |
And discourage the use of a explicit hie.yaml