docs: Add separate information about scripts #4643
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tgodzik
changed the title
|
Nice! Suggestion: add a link to/something along thelines of https://scalameta.org/metals/docs/troubleshooting/faq/#how-do-i-use-scala-2xx-for-my-script, I think it can sometimes be easy to lookover it there: emacs-lsp/lsp-metals#78 |
ckipp01
reviewed
Nov 16, 2022
We added some info in the previous release notes, but it's better to keep it in stable documentation. I think we can start moving some feature docs to features tab to be easier to discover.
Added a link to the FAQ at the bottom. |
ckipp01
approved these changes
Nov 25, 2022
Co-authored-by: LaurenceWarne <17688577+LaurenceWarne@users.noreply.github.com> Co-authored-by: Chris Kipp <ckipp@pm.me>
My eys were not successful in scanning the names 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We added some info in the previous release notes, but it's better to keep it in stable documentation.
I think we can start moving some feature docs to features tab to be easier to discover.