Rich Young

I encountered an issue with this behaviour that struck me as counter-intuitive, but reading through this issue I can see why it occurred. As @paulmillar states above, consider a use-case...

https://fetch.spec.whatwg.org/#credentials: > Credentials are HTTP cookies, TLS client certificates, and authentication entries (for HTTP authentication). [COOKIES] [TLS] [HTTP-AUTH] The [HTTP-AUTH] reference defines a number of header fields that could be...

Same, existing repos with no changes planned are fine, attempting to apply changes to an imported repository fails with this error. We've never enabled this feature.

Also encountered the same error a few days ago, for me in a fresh 5.45.0 plugin environment this does not cause an error during `terraform plan`.

> The "ambiguous_name" - "function_call" problem as mentioned above is a complete mess. My list of function.builtin is still incomplete, because it takes forever and a day to look them...

Before I wrote the yaml rules for Modern VHDL I spent a long time trying to implement a spec-compliant parser in various different parser-generator engines. The problem is more fundamental,...

Ah cool, sounds like a good plan to me. Give me a shout if you find anything weird in the YAML, I know there's an issue with loops I've yet...

Thank you for the suggestion, if the current set of snippets were duplicated with uppercase shortcuts to give uppercase keywords would that be suitable? There is unfortunately no easy way...

Take a look at https://github.com/richjyoung/vscode-modern-vhdl/commit/6be2381b9808b1581636ceec004e4e6e667d697e This adds a copy of all existing snippets with upper case shortcuts and keywords.

It makes sense and I'm working on functionality to enable this kind of behaviour in the future. The fundamental difference here is processing a file in the context of a...