Aleksander Heintz
Aleksander Heintz
I agree that it should be declarative. And overridable in child injectors.
What **could** work would be to create a "special" config symbol, which where global for all of the things. Say this symbol was named `di.CONFIG` (just for this example): ```...
I'd argue that configuration before instansiation of di is outside the scope of di, and rather inside the scope of angular, or whatever bootstraps the di. Otherwise you have to...
Let me try and explain a bit better then. The only real difference from my "special handling" of config (if we ignore the merging for now, and I'll get back...
Oh, and as for usage in angular, I would say angular has some `Config` method that's called before bootstrapping happens, that builds up the config "array", and uses it when...
But doesn't that mean you have 1 global (potentially HUGE) config object? And not one config object for Http, and one for Routing?
Yes, but you also go back to the (imho) icky convention-based way of doing config, where I have to either check some spec to see what the config name is,...
Well, yeah. That's probably true. It just feels a bit like we're back in magic string land, but that's just my opinion. Also, I think having config that depends on...
I'm not quite sure what your proposed solution is (I'm probably reading this wrong). Specifically what I'm trying to do is put `Tabs` into an `AppBar`. Problem is that `Tabs`...
@oliviertassinari In my mind that point is somewhat moot. Sure, when issues arrive, you add `xxClassName` (or `classes.xx` or whatever you end up deciding is the best path), but for...