#888 - Grower: new filter by amount of captures uploaded was added. #1032
Conversation
This file contains 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
OlhaD
commented
Feb 21, 2023
This was referenced Feb 26, 2023
* feat: also done for captures and verify contexts. also fixes 'first name' and 'last name' filters
…_filter Resolve merge conflicts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
#888 - Grower: new filter by amount of captures uploaded was added.
When I apply the filter, API is called with the parameters below:
https://dev-k8s.treetracker.org/query/v2/growers?capturesAmount_min=0&capturesAmount_max=0&limit=24&offset=0
https://dev-k8s.treetracker.org/query/v2/growers?capturesAmount_min=1&capturesAmount_max=25&limit=24&offset=0
https://dev-k8s.treetracker.org/query/v2/growers?capturesAmount_min=25&limit=24&offset=0
Issue(s) addressed
What kind of change(s) does this PR introduce?
Please check if the PR fulfils these requirements
Issue
What is the current behavior?
What is the new behavior?
Breaking change
Does this PR introduce a breaking change?
Other useful information