Cédric Luthi

Any chance you have a look, @glucaci and/or @nscheibe? It should be pretty straightforward, it's just another breaking change in the MongoDB driver, like #87. ¯\\\_(ツ)\_/¯

Ping @glucaci and @nscheibe. Any chance for a new release?

I'm a bit disappointed that #4751 was merged. One thing that I like in kiota is the tidy code which is generated, exactly like if it was written manually (except...

The `DirectoryInfo` class already has a [CreateSubdirectory](https://learn.microsoft.com/en-us/dotnet/api/system.io.directoryinfo.createsubdirectory) method and the `Directory` class already has a [CreateTempSubdirectory](https://learn.microsoft.com/en-us/dotnet/api/system.io.directory.createtempsubdirectory) method. So for consistency I think it's better to stick to `SubDirectory`. And now...

Oops, Qodana Scan is failing because of a [license error](https://github.com/fluentassertions/fluentassertions/actions/runs/10315788659/job/28556669106?pr=2718#step:3:32). 🙁 > License verification failed. Please ensure that the token provided through the QODANA_TOKEN environment variable is correct and that...

We're out of luck today! > 🚀 Posting coverage data to https://coveralls.io/api/v1/jobs [62](https://github.com/fluentassertions/fluentassertions/actions/runs/10514804928/job/29133501827#step:7:65) ⚠️ Internal server error. Please contact Coveralls team. And indeed, the [Coveralls status page](https://status.coveralls.io) acknowledges 500 errors....

Not sure what's happening with the coverage. [Build 10700844516](https://coveralls.io/builds/69600535) says that [AssemblyAssertions line 216](https://coveralls.io/builds/69600535/source?filename=Src%2FFluentAssertions%2FTypes%2FAssemblyAssertions.cs#L216) was uncovered. But looking at the base build, [AssemblyAssertions line 216](https://coveralls.io/builds/69561387/source?filename=Src%2FFluentAssertions%2FTypes%2FAssemblyAssertions.cs#L216) is NOT covered!

I juste rebased on `develop`. Qodana says _Not a valid commit name 659dc908b12957756e24c42c30fad924f3877ede_, I don't know why! I also changed the status of this pull request from draft to ready...

I tried to address everything, let me know if something needs more clarification.

On .NET 8, you can get rid of the `CS8669` warning by using `#pragma warning disable CS8669` instead of the more natural `#nullable enable`. ```razor @{ #pragma warning disable CS8669...