When splitting some F# code over multiple lines in a way that the F# compiler permits, Ionide syntax highlighting stops working correctly. It is particularly noticeable because syntax highlighting breaks throughout the entire file.
In particular, I'm facing issues when:
Splitting a qualified function reference over two lines:
Module
.f
rather than
Module.f
Splitting a record pattern-match in a function parameter over two lines:
let f ({ X = x
Y = y }) =
rather than
let f ({ X = x; Y = y }) =
git clone https://github.com/mattgallagher92/fsharp-syntax-highlighting-bugs.gitcd fsharp-syntax-highlighting-bugs/git checkout 44ee9c4f8aaf07cb5facc035581052b32c99e6fccode .MultilinePatternMatch.fs and SplitModuleAndFunctionName.fs and inspect the contentsgit clean -d -fgit checkout e074b183a43513f434ee3f652a711d0ed06d9821code .MultilinePatternMatch.fs and SplitModuleAndFunctionName.fs and inspect the contentsI expected syntax highlighting in the entire file to work when these constructs are split across multiple lines, in the same way that it works when the constructs are on one line.




Hey @mattgallagher92 :wave:,
Thank you for opening an issue. We will get back to you as
soon as we can. Also, check out our OpenCollective and consider
backing us.
https://opencollective.com/ionide
PS.: We offer
backersupport for all backers. Don't forget to addbackerlabel when you start backing us :smile:
It didn't fit into the nice concise bug report template you gave, but I just want to take the chance to note how awesome this VS Code extension is! The reason I'm raising the bug report is that writing F# with Ionide's lovely syntax highlighting is so much better 馃槉
Most helpful comment
It didn't fit into the nice concise bug report template you gave, but I just want to take the chance to note how awesome this VS Code extension is! The reason I'm raising the bug report is that writing F# with Ionide's lovely syntax highlighting is so much better 馃槉