Ci sono incappati di recente e concordo che non sia l’ideale; penso che la strada più semplice che possiamo percorrere per migliorare la situazione al momento sia creare una bozza con il contenuto del post respinto e collegare l’utente ad essa, in modo che possa modificarlo e pubblicarlo di nuovo.
Ho aperto una PR per aggiornare il comportamento qui:
main ← ux-requested-changes-draft
opened 09:39PM - 01 Apr 26 UTC
Currently when a post is queued for review, and the reviewer requests edits — we… send a message to the poster that looks like this...
>
> Hi username,
>
> We’ve reviewed your post in [example topic](#) and have some feedback for you.
>
> Reason: Does not meet posting guidelines
>
> Feedback: Moderator feedback goes here
>
> You can edit your original post below and re-submit to make the suggested changes.
> ___
> this is the original post content
> ___
> Thanks,
> Sitename Moderators
The problem with this is that "you can edit your original post below" isn't actually true — it's just the content of the post so you can copy and paste it into the composer and try again.
This change creates a new draft of the rejected content and links to the posting user's drafts, so they can more easily edit it and resubmit. This is a clearer flow than the current message.
The new message looks like this
> Hi username,
>
> We’ve reviewed your post in [example topic](#) and have some feedback for you.
>
> Reason: Does not meet posting guidelines
>
> Feedback: Moderator feedback goes here
>
> A draft has been saved with your original content. You can find it in your [drafts](/my/activity/drafts), make the suggested changes, and resubmit.
>
> > this is the original post content
>
> Thanks,
> Sitename Moderators
1 Mi Piace
