Explore the idea of marking the Data Builder DSL with @DslMarker to make it harder to make mistakes when trying to generate deeply nested types

[StylianosGakis]

Use case

When using the data builders, a common mistake that I do, (and apparently others do too) is that inside the data builder, and especially when I am nested quite a lot, there are a lot of builders at the time in the scope; aka this refers to a lot of builder types.
This makes it easy to reference something from a higher up scope, resulting in confusing looking code if you seemingly set some field that is not present in your correct scope, but it comes from a higher up one.

This comment shows an example of this.

Describe the solution you'd like

Marking the generated DSL builders with @DslScope would most likely make this mistake a build-time error, making our life just a bit easier when working with this feature.

[martinbonnin]

This is now available in 4.2.0. It was actually really simple, I'm ashamed it took so much time. Apologies for the delay!

[github-actions]

Do you have any feedback for the maintainers? Please tell us by taking a one-minute survey. Your responses will help us understand Apollo Kotlin usage and allow us to serve you better.

[jamesonwilliams]

Ah, this is a good one. We had a ton of invalid data builder assignments. 😄