Florian Bernd

@gmarokov Is that solution still valid? I'm trying to use your tool like: ``` .\.sonar\scanner\dotnet-sonarscanner begin /k:"AUTHORED" /o:"AUTHORED" /d:sonar.login="${{ secrets.SONAR_TOKEN }}" /d:sonar.host.url="https://sonarcloud.io" /d:sonar.cs.vscoveragexml.reportsPaths=coverage.xml /d:sonar.testExecutionReportPaths=SonarTestResults.xml dotnet build --no-incremental dotnet-coverage collect "dotnet...

Hi @DR9885, thanks for the feature request. This was as well mentioned in #8150 as far as I remember. I'll keep your dedicated issue open anyways to allow for upvotes....

Hi @hainest , interesting question! Yes, the regression tests and the fuzzing are the only tests specifically for the decoder / formatter. I'm definitely open to improve the tests, however...

This feature had an unmet [requirement](https://github.com/elastic/elasticsearch-specification/issues/2049) for quite some time. The missing functionality got finally implemented on specification side, but currently still misses support on the code generator.

This will be released in the next version 9.1.12 and 8.19.11.

Hey @niemyjski, thanks for the feedback. This format works perfectly well for me! I'll have a detailed look in a few hours :-)

@niemyjski ## 1. Ah, I see. This does not work, because all (most) of the fluent methods are using this signature: ```csharp public SearchRequestDescriptor Query(Action action) ``` The instance of...

Hi @tdoman , this sadly seems to be one of the places where the new generated client lacks a bit of the convenience of NEST. There is no trivial solution...

9.0 is around the corner (a few weeks). I'll hope to add fluent support in that release. It will contain quite a few improvements related to descriptors anyways.

Hi @stefanobranco, 1. The aggregation change requires a little bit of additional code, but on the same time this new structure maps closely to the corresponding [JSON request](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations.html). This is...