[#17] - fluent builder improve sdk usability#24
Merged
https-richardy merged 16 commits intoApr 24, 2026
Conversation
…y parameters, improving the SDK's usability
…y parameters, improving the SDK's usability
…y parameters, improving the SDK's usability
…y parameters, improving the SDK's usability
…y parameters, improving the SDK's usability
…y parameters, improving the SDK's usability
…y parameters, improving the SDK's usability
…ing query parameters, improving the SDK's usability" This reverts commit a2402bb.
… parameters, improving the SDK's usability
…order to synchronize the SDK version. Contracts with the SDK
https-richardy
deleted the
feature/17-fluent-builder-improve-sdk-usability
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The goal of this improvement is to make the SDK more intuitive and pleasant to use in day-to-day scenarios, reducing the need to manually construct parameter objects and improving the overall clarity and expressiveness of the API.
Currently, using parameter models directly requires manual object initialization and explicit property assignment, which can become verbose and less readable as the number of filters grows.
By introducing a fluent builder approach, the intention is to allow developers to construct parameters in a more readable and intention-driven way, while also improving discoverability through the API itself.