Data masking #3556
Description
Use case
Are there any plans to implement fragment data masking? My understanding (based on a chat with Claude) is that the generated classes include fields that are only available via fragments. Is that accurate? It seems like it shouldn't be very difficult to just not recurse into fragment spreads when generating these classes.
Describe the solution you'd like
for
fragment Foo {
name
...Bar
}
fragment Bar {
age
}
I would like the Foo class to not have a age field