@named() about get_it

[anaisbetts]

I think it's a good idea, because otherwise you end up having to make bogus types for silly reasons:

// The type here is `string`, a very common type!
locator.registerSingleton("http://the/url", name: "ServiceURL");

vs:

// ugh ugh ugh
class ServiceUrlContainer { ... }
locator.registerSingleton(ServiceUrlContainer("http://the/url"));

[escamoteur]

Implemented in V1.1.0

[escamoteur]

Hmm, not sure if I like it here. @anaisbetts what do you think?

[S26T]

for example:

need to add some sharedpreferance objects, but different by key name.

SharedPreference sp1 = SharedPreference(Key1, mode);
SharedPreference sp2 =
SharedPreference(Key2, mode);

[lukepighetti]

New to service locators but that seems like an anti-pattern for get_it to store strings instead of something like a resources service.

[anaisbetts]

@lukepighetti Probably, there are more compelling examples though of objects that are difficult to differentiate solely on type. For example, if you have a DiskCache interface, you might want the InUserProfile and TemporaryCached instances, even though these are implemented by the same type