I'm using getAll<>() to retrieve a list of d...

# koin

[Jayvijaysinh Gohil]

I'm using getAll<>() to retrieve a list of dependencies, but I also need the named value for each. How can I accomplish this? My goal is to create a map where the key is the named value and the value is the dependency itself.

[withoutclass]

Use a sealed class or enum instead of string names

[Jayvijaysinh Gohil]

Not possible in my case. I'm implementing deep links in my application along with Slack's Circuit. The map I'm creating uses the deep link string representation as keys, which precludes the use of enums or sealed classes for this purpose.

[withoutclass]

No it doesn’t, use the string value as an enum or sealed class property 🙂

[Jayvijaysinh Gohil]

Can you share a skeleton code example if possible? 🙂

[withoutclass]

https://kotlinlang.org/docs/enum-classes.html

[withoutclass]

The docs are good, and have examples of adding properties to enums

[Jayvijaysinh Gohil]

I meant how would I get them along with getAll to create a map as opposed to using strings.

[withoutclass]

Sorry, that’s for you to figure out

[withoutclass]

If it were me I would never use strings at all, they are not safe, and any solution that chooses to use strings for important things like navigation or parameters is asking for pain

[Jayvijaysinh Gohil]

Oh, I see what you mean. I was under the impression that using enums instead of strings would allow me to access them through a Koin API, but it seems it was more of an architectural suggestion. Thanks for the suggestion. 🙏🏻

[withoutclass]

No, my suggestion was to take your strings, and wrap them in an Enum

[withoutclass]

then use the enum to fetch the dependencies from koin

[withoutclass]

you can use Enums/types as qualifiers

[withoutclass]

If you are stuck using Strings for things, you can do things to make them more safe 🙂

[withoutclass]

That or something else with your architecture should change so that you can handle all of this with a single factory and a parameter

[withoutclass]

then you can handle the mess within the implementation class