Ensure deleted user slug is pseudonymized too (fix #2016) #2049
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 fixes #2016 by pseudonymizing the slug too on deletion (will be
deleted-XXX
whereXXX
is sequential)Possible alternatives:
deleted
deleted
deleted
(ie.deleted-ae7f89
)deleted-2019-02-25
but collision are still handled bySlugField
so in case of multiple deletion it will bedeleted-2019-02-25-1
,deleted-2019-02-25-2
....)