ExpandWildcards serialized with incorrect casing in Elastic.Clients.Elasticsearch 8.19.0-preview.1

[Ramstad]

Elastic.Clients.Elasticsearch version: 8.19.0-preview.1

Elasticsearch version: 8.18.1

.NET runtime version: net9.0

Operating system version: Windows for client, docker for elasticsearch

Description of the problem including expected versus actual behavior:
After downgrading from client version 9 to 8.19.0-preview, I get an error when deleting indexes with wildcard.
Request done like this:

client.Indices.DeleteAsync<DeleteResponse>("my_index_prefix*", descriptor =>
            {
                descriptor.ExpandWildcards(ExpandWildcard.All);
            }, TestContext.Current.CancellationToken);

I get this error:

Invalid Elasticsearch response built from a unsuccessful (400) low level call on DELETE: /my_index_prefix*?expand_wildcards=All
 Exception: Request failed to execute. Call: Status code 400 from: DELETE /my_index_prefix*?expand_wildcards=All. ServerError: Type: illegal_argument_exception Reason: "No valid expand wildcard value [All]"

The only difference I can see from version 9 to 8.19.0-preview is the casing of the all/All value.

[flobernd]

Hi @Ramstad thanks for reporting.

This is interesting since these client versions do share the exact same code foundation.

I probably forgot to backport a detail. Will have a detailed look as soon as I have time.

[Ramstad]

I did some digging and found that it was due to the change done in the transport: UrlFormatter
So it seems I didn't encounter the bug on version 9 as I only was at 9.0.3 and not 9.0.4

[flobernd]

Thanks for checking! We have to add back the branch that honors custom EnumMemberAttributes.

[flobernd]

Fixed in 8.19.0-preview.2.