PostgrestBuilder refactoring and improvements
#3
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.
What kind of change does this PR introduce?
Refactor, improves current code.
Additional context
Hi, I'm willing to use these packages on one of my side projects, and while reading the code base, I found some room for code improvements and I decided to contribute by opening this PR.
These changes introduce only refactor and should not have the behavior changed.
Improved items
executemethod ofPostgrestBuilderclass.guardwhenever sounds better on classPostgrestBuilder.appendSearchParamsis called.URLRequestthat are built by the builder classes (this is a suggestion on how to easy test the Builders)