这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@sam-tombury
Copy link

No description provided.

(odoc :with-doc)
(odoc-parser (= 2.0.0))
(merlin-lib (= "5.2.1-502+jst"))
(merlin-lib (= "5.2.1-502+ox"))
Copy link
Author

Choose a reason for hiding this comment

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

This corresponds to the published version on the OxCaml opam-repository, but there might be some broader changes needed to support that

}
; syntax_documentation = Some { enable = false }
; merlin_diagnostics = Some { enable = false }
; merlin_diagnostics = Some { enable = true }
Copy link
Author

Choose a reason for hiding this comment

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

Configuration of this setting isn't possible in many LSP clients (e.g. the ocaml-platform VS Code extension), and defaulting to true seems to match the previous behaviour. I guess the false default might make sense in the JS internal toolchain

~referencesProvider:(`Bool true)
~documentHighlightProvider:(`Bool true)
~documentFormattingProvider:(`Bool false)
~documentFormattingProvider:(`Bool true)
Copy link
Author

Choose a reason for hiding this comment

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

As above, this probably makes sense in the JS internal toolchain but isn't configurable by clients. Editor formatting (via the LSP) does work as expected (with version unset in .ocamlformat) with this capability enabled


let exec cancel bin args stdin =
let refmt = Fpath.to_string bin in
let refmt = Stdune.Path.to_string bin in
Copy link
Author

Choose a reason for hiding this comment

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

This change might not strictly be needed

@btwied
Copy link

btwied commented Aug 22, 2025

This was just brought to my attention. The merlin_diagnostics setting should probably default to true; this was an oversight, since our editors provide that setting internally. @sam-tombury: is there a reason you closed the request?

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