Will Rowe
Will Rowe
@drjayvee > Oh, do I understand correctly that you'd want the default value in var to apply exclusively to injected variables, not ones created using set and macro arguments? Yes,...
There are some issues with multi-line arrays/maps that could also be causing this.
As mentioned in https://github.com/sublimelsp/LSP/pull/2498, this would require [WorkspaceEditClientCapabilities.resourceOperations](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspaceEditClientCapabilities) to be implemented by [sublimelsp/LSP](https://github.com/sublimelsp/LSP)
This is very frustrating to deal with.
It seems that Twig is matching the default behavior of PHP when using `in_array`. The behavior you are expecting would be the case when passing `true` as the second argument...
@gorenstein I'm saying that `in_array` would be the PHP equivalent and that `true` is not unexpected since it's a loose comparison. Similarly, using `==` in Twig is a loose comparison...
I don't see any issue with this since the option is disabled by default. It gives an upgrade path for the next major version to change the default. May be...
@fabpot is the new terminology `variables` as opposed to `context` or does `context` have a different meaning?
I thought @derrabus meant a flag in the configuration, like how you can ignore missing variables.
I believe several attempts have been made to add an `@attributes` helper in the past. One of which is #52783.