Closed nightblure closed 3 months ago
@nightblure thank you! interesting case. Will think about it
@nightblure will it be hard? I'm not sure, that this feature will be popular, but I don't mind if you want to do it
@nightblure will it be hard? I'm not sure, that this feature will be popular, but I don't mind if you want to do it
I don’t know about popularity, but I think it’s necessary for reasons of convenience
Let's imagine that your service actually has a lot of environment variables and other configuration data. This is usually stored in the form of dataclasses or identity models obtained as a result of parsing environment variables and various configuration files (for example, yaml configs, etc...). And in order not to store a bunch of fields in one class, you can often find division into subclasses for reasons of convenience and logical grouping of variables. Based on this, in some cases this functionality would be necessary. Otherwise, we would have to make a bunch of small providers instead of one or another kind of refactoring
btw dependency injector can do this: https://python-dependency-injector.ets-labs.org/providers/provided_instance.html
@nightblure valid points
Hey!
I found some problem in attr getter. It lies in the fact that it does not know how to work with nested attributes. Just look at some tests below and you'll understand what we're talking about.
I think I can fix this if you want these cases to work