[FEATURE] Add client overloads accepting descriptors

[b93rn]

Elastic.Clients.Elasticsearch version:
8.08

Why do i need an Action<SearchRequestDescriptor> like shown below?

public virtual Task<SearchResponse> SearchAsync(Action<SearchRequestDescriptor> configureRequest, CancellationToken cancellationToken = default);

Request:
Add overload <SearchRequestDescriptor as the NEST client had.

[stevejgordon]

Thanks for raising this, @b93rn. This is a gap we should close. I'll look to amend this in our code generation so that the extra overloads are included.

[svenhartmann]

I also missed this but the migration from a NEST SearchDescriptor to a 8.x SearchRequest with Object initializer syntax can be done in a short amount of time.

Maybe this helps you to get your work done without having the feature yet.

[b93rn]

I also missed this but the migration from a NEST SearchDescriptor to a 8.x SearchRequest with Object initializer syntax can be done in a short amount of time.

Maybe this helps you to get your work done without having the feature yet.

This comment might push me in the right direction. My thoughts were that SearchReqeustDescriptor is the equivalent of SearchDescriptor in NEST?