budgeting//contrib/filters: add random ordering to ProposalFilterSet … #4582
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.
…and rename filter in api to be able to pass it
depends on liqd/adhocracy4#1246
fixes #4574
I had to add the daily random sorting to the list view as otherwise the annotations dont work and thus dont show up in the map pop ups. To make it work with the api filter, I had to change the wording there to be consistent with the wording in the list filte in a4.
The daily random sorting is different for the django list and react list, that is because in the react list we are only ordering the proposals of a certain module whereas in the django list, the ordering is determined on all proposal in the db and then later the proposals are filtered for the module. I did not dare to touch that as that is deep in a4 and django. But since we will always have either or, it should be fine?