-
Notifications
You must be signed in to change notification settings - Fork 660
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make enum as sealed class Unknown constructor opt-in #5813
Conversation
✅ Deploy Preview for apollo-android-docs canceled.
|
I'd vote yes here to make the intent really clear. There might be use cases where opting-in is desirable and we'll guarantee the API while opting-in Maybe Ping @StylianosGakis any preference? |
I think a separate annotation makes sense yes. Exactly because it may be something that you may want to opt-in without it being the "wrong" thing to do. While using something ApolloInternal should always be the "wrong" thing to do. |
...tations/src/commonMain/kotlin/com/apollographql/apollo3/annotations/ApolloEnumConstructor.kt
Outdated
Show resolved
Hide resolved
...tations/src/commonMain/kotlin/com/apollographql/apollo3/annotations/ApolloEnumConstructor.kt
Outdated
Show resolved
Hide resolved
…raphql/apollo3/annotations/ApolloEnumConstructor.kt Co-authored-by: Martin Bonnin <[email protected]>
…raphql/apollo3/annotations/ApolloEnumConstructor.kt Co-authored-by: Martin Bonnin <[email protected]>
Related to #5796
This uses
@ApolloInternal
- should we introduce a dedicated annotation instead?