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

First attempt at documenting serverIdleTimeout #1222

Merged
merged 1 commit into from
Sep 15, 2024

Conversation

lervag
Copy link

@lervag lervag commented Sep 10, 2024

This is not ready for merge. There are a few questions:

  1. Is this the correct place to add this type of reference?
  2. Is it the correct way to document it?
  3. Should I format it differently?

I would not mind completing this and perhaps try and include a few more settings when I'm at it.

Please see discussion at sbt/sbt#7631.

@eed3si9n
Copy link
Member

Yea. I guess we don't yet have user-facing sbt server page, but I think this is fine for now.

@@ -332,3 +332,16 @@ This will respond back with the result of the action.
[lsp_initialize]: https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md#initialize
[lsp_initialized]: https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md#initialized
[lsp_publishdiagnosticsparams]: https://github.com/Microsoft/language-server-protocol/blob/master/protocol.md#publishdiagnostics-notification

### Configuration
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should go immediately after the intro, like at line 17.

@eed3si9n
Copy link
Member

Also could you target 1.x branch for sbt 1.x documentation plz?

@lervag lervag changed the base branch from develop to 1.x September 15, 2024 21:13
@lervag
Copy link
Author

lervag commented Sep 15, 2024

I believe I've made the suggested changes.

Should we include more options here before considering a merge? If so, are there any particular ones that seem more important?

@eed3si9n
Copy link
Member

Should we include more options here before considering a merge? If so, are there any particular ones that seem more important?

I'd say ship first and we can add more later.

@eed3si9n eed3si9n merged commit f35366d into sbt:1.x Sep 15, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants