Use Group clause in ExportLensActionRequest to allow for aggregate Lens exports #127
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.
As per issue #90 - when using an export query that is not
forAllMatchingResources
, the default behaviour was to use the LaravelwithKey
which selects the primary key (usuallyid
) of the Resource in question, disregarded the key of the Lens for that resource (which may be an aggregate lens usingCOUNT()
andGROUP BY
SQL)The solution is to check for a
groups
clause in the Lenses underlying query builder, and if it exists, to use that with awhereIn()
instead