Wrong colorization after "type" even if it's not a standalone word about ionide-fsgrammar HOT 5 CLOSED

No problem :)

Yes, sometimes I think VSCode is failing to update properly the extension. For example, sometimes I have some files missing...

from ionide-fsgrammar.

I can't reproduce the problem with latest Ionide.

Can you please check if you have still have the problem in an empty file. Something like:

module Test

let self =
    if self.process_type <> OderToPay && self.process_type <> InvoiceToPay then
        ""
    else
        ""    

Or if my hand written code is testing the wrong thing :)

from ionide-fsgrammar.

Yes, unfortunately it's still happening :/ You can test with:

type Foo =
    { process_type: string }

let test() =
    let self = { process_type = "foo" }
    if self.process_type = "foo"
    then failwith "WTF!"
    else self

Maybe adding a boundary condition to "type" in the regex (like \btype)?

from ionide-fsgrammar.

I still can't repro it...

And we are already protecting type with a word boundary source

The word boundary has been added because @selketjah reported a similar issue to yours. Related commits

Can you please check the version of Ionide you are using ? Or perhaps try to uninstall and reinstall it to be sure all the files are using latest version.

Last solution would be for you to clone ionide-fsgrammar, open it in VSCode and press F5 to check if you are still able to reproduce the synthax error.

from ionide-fsgrammar.

Ah, yeah! Uninstalled and reinstalled Ionide and it's working fine now. Weird, I thought extensions were automatically updated now. Sorry for the hassle!

from ionide-fsgrammar.