WIP functional variants of the select, where and having query builder methods #215
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.
stacked on #185
In the old query builder you could call the same methods with a callback for the functional behaviour, but with the new query builder its always a callback with makes the api very hard to function as both an expression builder or functional callback. Because of that I think it's best to split these variates out as distinct functions.
For this first pass I have namespaces these under
.fn
on the query builder, but we could have then on the main object with a prefix/suffix.I like the namespace as it nicely groups them as well as moving deeper in the editor prompts, somewhat demoting them to a second tier.
Looking for feedback on this before finishing touches (if were happy its 95% done)