feat: introduce Map.share_status=DRAFT and DELETED #2357
Merged
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.
This PR introduce two new share_status:
DRAFT
andDELETED
.So all status are now:
Here are the impact of such introduction, on the draft side:
UMAP_DEFAULT_SHARE_STATUS
Note: add the end
DRAFT
andPRIVATE
are very similar, but I made the choice to keep the two, so one can still distinguish their draft maps from their ready map they want to keep private.On the delete side:
share_status=DELETED
, which act as a sort of trash; so it become easier to recover a map, with it's full datalayers, etc. (the only thing which will not be restored is the previous share_status, which should be draft again after a restore; the restore function itself is not implemented)empty_trash
which delete for real maps in DELETED status and with last_modified > 30 days (by default, can be changed with a command line argument)restore
function, which for now can be done by simply changing the share_status from the shell or the admin)fix #2207