After/AfterKey dictionary types in Composite Aggregation/Aggregate

[gpetrou]

Elastic.Clients.Elasticsearch version: 8.13.10

Elasticsearch version: 8.11

.NET runtime version: 8.0

Operating system version:

Description of the problem including expected versus actual behavior:
CompositeAggregate has an IReadOnlyDictionary<string, FieldValue>? AfterKey property.
CompositeAggregation has an IDictionary<Field, FieldValue>? After property.

Should these dictionaries have the same <string, FieldValue> types instead?

Steps to reproduce:
1.
2.
3.

Expected behavior
A clear and concise description of what you expected to happen.

Provide ConnectionSettings (if relevant):

Provide DebugInformation (if relevant):

[flobernd]

Hi @gpetrou,

the generator flattens alias types like Field in responses as that makes usage easier in most cases. This place is special as that prevents us from passing the AfterKey dictionary directly to the After value for pagination.

I'll see what I can do here.