Open MariaSolOs opened 9 months ago
I did a search for inline .* hints
in the F# repository and came across the following terms:
I don't know if there are more.
Questions:
To me, it would seem best that any change like this would change the code as well and not just documentation and user facing strings.
Questions:
- @MariaSolOs Should "inline" be replaced with "inlay" in all three of these?
That's the goal.
- @MariaSolOs Is this the relevant documentation for inlays? https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint
Yes.
- Where else would need these changes? Any documentation outside of the F# repository?
This issue is scoped to this repository only, so don't worry about that.
To me, it would seem best that any change like this would change the code as well and not just documentation and user facing strings.
Agreed, but huge renames like these might involve a huge refactor which I leave to the core maintainers of this repo to decide if it's worth it.
Thanks for the clarifications! Just wanted to make sure all three of those were in the same category.
Using the web-based VS Code on the F# repository and searching for the regular expression inline.*hints
yields 185 entries, so it doesn't seem too bad to do it all in one go. Only 40 of them, across 10 files, are in .fs
files.
I'd be willing to make this change. It seems like effectively a find and replace and then 🤞 that tests pass task (?), from what I can tell.
For consistency with LSP and VS Code, user visible references to "inline hints" should use "inlay hints" instead.
Related change in Roslyn: https://github.com/dotnet/roslyn/pull/71855