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
{{ message }}
This repository has been archived by the owner on May 29, 2024. It is now read-only.
The HTTP PUT functionality currently allows an Event to be updated, including setting the 'updated' flag to 'edited' or 'deleted'. When this happens, the whole Event must be sent again, with modifications, and it is updated in its entirety. This is because when we delete (for example for Twitter compliance reasons) we only need to remove the Twitter-sensitive data and can leave the rest behind.
In some cases a consumer may wish to simply mark an Event as being deleted without modifying it. In this case, all that is required is the updated_reason.
Implement an HTTP DELETE endpoint that is able to accept only an updated_reason field, and will merge the updated, updated_date and updated_reason with the previous Event's data.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The HTTP PUT functionality currently allows an Event to be updated, including setting the 'updated' flag to 'edited' or 'deleted'. When this happens, the whole Event must be sent again, with modifications, and it is updated in its entirety. This is because when we delete (for example for Twitter compliance reasons) we only need to remove the Twitter-sensitive data and can leave the rest behind.
In some cases a consumer may wish to simply mark an Event as being deleted without modifying it. In this case, all that is required is the
updated_reason
.Implement an HTTP DELETE endpoint that is able to accept only an
updated_reason
field, and will merge theupdated
,updated_date
andupdated_reason
with the previous Event's data.The text was updated successfully, but these errors were encountered: