Kevin Schaal

Ah, now I understand your approach. As you pointed out, no dummy final method would be needed. However, the downside is that the extension method remains available after the instance...

I am not convinced that this feature should be included in the fluent API library. Since these extension methods are relatively simple and unordered, they can be added directly as...

Hi @oformaniuk, Thank you for your suggestion! I see a conceptual issue with the expected behavior in your example. The `WithHeader` method can either return the `IWithHeaders` interface to add...

I revisited this issue and came to a different conclusion. I now believe that `FluentSkippable` behaves as expected in this scenario. Once the step decorated with `FluentSkippable` is reached, it...

Hi @mikej0 , Thank you very much for this request. `async` is not yet supportet, there is currently no way to make the builder return a task. However, it should...

Hi @mikej0, I was looking into this issue and noticed that using an async `FluentMethod` in combination with `FluentReturn` in the last step is already working. I have updated the...

Hi @mikej0 , Thank you for your suggestions! Currently, an async method is only possible in the final step. This method can return any type wrapped in a Task. You...

Hi @chrisbewz, Good catch, thank you for reporting this! I’ll work on a fix soon. Best regards, Kevin

Hi Mike, Thank you for your suggestion! I see the benefit of introducing a new step between two existing steps without modifying the latter. Your proposed solution could work well...

Semver or an array approach is interesting, but would require additional Fluent Attribute constructors. I lean towards keeping the API slim and simple. The double approach is effectively equivalent to...