Daniel Hahler

btw: I've forked the plugin at https://github.com/blueyed/vim-autoclose and improved it some. You may be interested to try it out, not just for debugging or fixing it, but also because I...

If the BufEnter event seems safe, do you plan to add support for scanning it? Do you see any other way the plugin in question (vim-autoclose) might get changed/improved? It...

> are you sure that `strawberry_django` forthis should work just like `strawberry_django` forces the type annotation to optional? Can you please rephrase / fix your question? :) I cannot really...

Yeah, that fixes it. Thanks! Might be worth adding to the documentation? (where?) Could it also be detected and handled with a clearer error message then?

Unfortunately it also causes `only` to not be applied/considered. Do you think this could that be done/handled? It's likely because it is not on the concrete class itself, but via...

> side effects? There are.. For now I can work with using `only={"foo__archived"},` to help the function, which uses that property.

@bellini666 I think model properties do not help here: the issue is that there is a property, which returns a special "Bar" object via a property/function, and the optimizer does...

This is related to https://github.com/blb-ventures/strawberry-django-plus/issues/154, i.e. it is with a non-model field, and specifying `field_name` fixes it / helps there.

> Is that `special_bar` a property? Yes. It's to a FK's property, which I am turning into an actual field, but `field_name="bar__special"` is not supported (no splitting by field separators).....

I think having to specify `only` as a workaround should/could be handled automatically.