I get a warning: Extension is shadowed by a member Is there some magic annotation which makes the ex...

# getting-started

[Norbi]

I get a warning: Extension is shadowed by a member
Is there some magic annotation which makes the extension higher priority than the member?
Thanks.

[Joffrey]

How would you expect it to work? What if the extension is not imported? You can't force consumers to add an import I guess, or it's no longer a matter of priority.

[Joffrey]

Why not just name the extension differently? What are you trying to do?

[Norbi]

You are right, I didn't think about it 😅
I'm creating a more-or-less type-safe wrapper around the JPA EntityManager .
In my TypeSafeEntityManager: EntityManager sub-interface I have overridden createQuery() to require opt-in:

@NotTypeSafeJpaApi
override fun createQuery(qlString: String): Query

But I also wanted to create an extension function:

inline fun <reified T : Any> TypeSafeEntityManager.createQuery(qlString: String): TypeSafeQuery<T> = ...

Never mind, I will do something else, thanks for the answer 🙂

[Norbi]

> What if the extension is not imported?
What I wanted is:
• if the extension is not imported then the member is used (which requires opt-in)
• if the extension is imported then it would have higher priority (magically 🙂)

[Joffrey]

Then I guess your best course of action here is just to use another name for your extension

[Joffrey]

You could even use a @Deprecated annotation instead of requiring opt-in, this way you can use ReplaceWith to automatically replace the call

[Youssef Shoaib [MOD]]

I think also implementing EntityManager might not be what you want if you're trying to stop users from calling the unsafe methods. Instead, you can have a @NotTypeSafeJpaApi val manager: EntityManager exposed.

[Joffrey]

Yeah actually using a wrapper/decorator pattern would be a better approach

[Norbi]

EntityManager exposed

Good idea, thanks!