@experimental -> @requiresOptIn

[martinbonnin]

Rename @experimental to @requiresOptIn

Also:

• support renaming @targetName
• add tests that read the opt-in annotations using reflection

[BoD]

I know this is all still "cooking" :) but it would make sense to have a mapping (feature -> annotation) instead?

So for instance

type Foo {
  field: String
  betaField: String @requiresOptIn(feature: "beta")
  alphaField: String @requiresOptIn(feature: "alpha")
}

could generate

data class Foo(
  field: String,
  @Beta
  betaField: String,
  @Alpha
  alphaField: String,
)

[martinbonnin]

Yep, good point. Ultimately, I think we'll want to do this with GraphQL configuration, not Gradle configuration:

extend directive @requiresOptIn @map(feature: "alpha", annotation: "com.example.Alpha")
                     @map(feature: "beta", annotation: "com.example.Beta")

or if we decide to go the "markers" road:

directive @alpha on FIELD @requiresOptIn
directive @beta on FIELD @requiresOptIn

extend directive @alpha @targetName(name: "com.example.Alpha")
extend directive @beta @targetName(name: "com.example.Beta")

What do you think?

[BoD]

Oh yeah doing this with GraphQL is nice! I guess it'll depend on which direction the RFC goes but both approaches look good to me :)

[netlify]

✅ Deploy Preview for apollo-android-docs canceled.

Name	Link
🔨 Latest commit	9c65662
🔍 Latest deploy log	https://app.netlify.com/sites/apollo-android-docs/deploys/629f8f65eeeb1600099f0cd5