Steve Kuznetsov

We need to consider the flow: 1. sever has version v1, updates to v1 (no change) but adds a backwards-compatible field 2. client has naive deserialization, drops new field 3....

@chlowell were you aware of the conversation happening on https://github.com/Azure/azure-sdk-for-go/issues/20571? Sorry if I was not clear - I 100% agree with you that the changes here as they are will...

Rebased after pre-requisite PR merged.

Would be great to do it but not sure if maintainers want this feature.

If this proposal is acceptable, I am happy to implement such a thing, also happy to hide it behind a flag.

@omissis any thoughts on this? Happy to start work ASAP if you are OK with the idea.

@omissis wouldn't the transition from a one-length anyOf to a n-length anyOf just mean that the generated code would change from something like ```go type Thing struct { Member MemberType...

@omissis thoughts? On coding this I realized we just ignore these fields today. The update would be trivial: ```diff $ git diff -- pkg/generator/schema_generator.go diff --git a/pkg/generator/schema_generator.go b/pkg/generator/schema_generator.go index 25bea18..24d384c...

@omissis any thoughts here?

@omissis any chance you have feedback on this?