You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the way we remove protests is by deleting them from the collection.
It's better if we add an archived property to it instead. It'll require changes across all source code (wherever we fetch protests we need to add an archived != true condition to it.
We'll probably need to add a migration that adds the archived property to all existing protests (it'll make it easier to run conditions on the collection).
The text was updated successfully, but these errors were encountered:
I believe that in the current admin flow what you're describing already happens. You can archive an approved protest and it adds to it archived: true. All that remains is to filter it out on our api requests
Currently, the way we remove protests is by deleting them from the collection.
It's better if we add an
archived
property to it instead. It'll require changes across all source code (wherever we fetch protests we need to add anarchived != true
condition to it.We'll probably need to add a migration that adds the
archived
property to all existing protests (it'll make it easier to run conditions on the collection).The text was updated successfully, but these errors were encountered: