Maxime Mangel
Maxime Mangel
@ncave `Fable.PublishUtils` is not used by Fable release pipeline. It is used by other repository inside of Fable org like [fable-browser](https://github.com/fable-compiler/fable-browser) or [Fable.Node](https://github.com/fable-compiler/fable-node). And I am planning to move these...
> To clarify, I really appreciate your efforts and taking on the burden of publishing, and I want to help as much as I can. So anything that can simplify...
> We'll have to do a lot of conditional work to get there though, as feature/API support differs a lot between languages. Indeed, this is the big issue I see...
This bug seems to be coming from FSAC. When inspecting the tokens it seems like the range for the semantic token are off:   It seems like Visual Studio is able to handle that code correctly:...
No disagreement with this approach. I believe this is why we also have different `CommentStyle`: https://github.com/fsharp/FsAutoComplete/blob/4bc676cc1e8659d9338d31d82d6244bcfcc55cc4/src/FsAutoComplete.Core/TipFormatter.fs#L715-L720 I suppose in the case of `Emacs` we should the client to say that...
Yes, this is what I think too. I am just unsure if we already have the style corresponding to: > and we could default to a style that is more...
Yes `Open the documentation` is VSCode specific only so this part is similar to this issue. I think you are seeing the complete documentation here but the formatting is not...
I am wondering why we are seing this issue now, it has been like that for a long time. > This PR sets `DisableImplicitFSharpCoreReference` to false, this pins `FSharp.Core` to...
@PierreYvesR Thanks for the clarification. It strange that even when we ask to not have dependencies against something, there still are some reference to it and have it updating... Because,...