Hello! Due to an unfortunate decision in the past,...

# apollo-kotlin

[Eduard Boloș]

Hello! Due to an unfortunate decision in the past, we have an enum value with the name UNKNOWN__, meaning that now we can't switch that enum to use a sealed class in Kotlin, because of the name clash between the object and the class 🤦 What would be the easiest/fastest way to change the generated classes' name to something else, to avoid the conflict? Is a compiler hook the only way?

[Stylianos Gakis]

I bet the name “UNKNOWN__” was picked in apollo-kotlin because everyone was thinking that surely nobody would have named something that, so there is no way this ever breaks anybody 😂
And here you come to break that assumption

[mbonnin]

It was a pretty bad decission in retrospect, the __ should have been at the beginning (GraphQL has reserved all identifiers that start with __ )

[kevin.cianfarini]

import apollo.blah.UNKNOWN__ as ApolloUnknown

[kevin.cianfarini]

Would that work?

[mbonnin]

There's @targetName for those cases, let me check

[mbonnin]

https://specs.apollo.dev/kotlin_labs/v0.3/#@targetName

[kevin.cianfarini]

Oh I see, the enum is named unknown in their graphql schema. I misunderstood.

[mbonnin]

There's an example here

[Eduard Boloș]

Whatever the name Apollo would've picked, we'd have used the same. This was a really bad way to handle on our backend unknown enums sent as an input from old clients 🤦‍♂️

[Eduard Boloș]

I'll have a look, thanks!

[Eduard Boloș]

It worked!!!!! Thank you so much, that was so easy 🙂
And I got so many replies in such a short timeframe. This community never ceases to amaze me apollo ❤️