Seth Coussens

We are seeing the same issue now with no configuration changes on our side. It only started recently.

For our part, we are using the latest available on Azure DevOps which is version 4.* or so it says. We had to put in an option to not look...

@marceloverdijk while this doesn't solve whatever the underlying issue in the code is... you can follow one of the examples to implement a fuzzy filter that replaces the global and...

I'm seeing this same behavior, but have the additional issue in that automatically organizing imports (which many people do on save), doesn't alphabetize them, and then it causes this area...

Just to confirm, organizing the list imports by identifier and not path does resolve this...