3 ms·
If I understand your solution correctly, does it mean that it's now the client's obligation to get the content from the revert-to version and create a new versi
by kailuowang 13y ago
If I understand your solution correctly, does it mean that it's now the client's obligation to get the content from the revert-to version and create a new version and POST it to /posts/X/versions? That should work, but what if I don't wanna give the client the ability to create version arbitrarily (only allowed to revert to a pre-existing version)?
- mtrimpe 13y agoMy first solution was assuming you could not revert. If you want to allow revert then the client would first call /posts/X/versions, get a list of all versions and then either do PATCH /posts/X { "version": "older-revision" } or PATCH /posts/X/versions/older-revision { "active": true } Access control is completely orthogonal to this; so for your sample case you would just return a 403 for any other calls (like e.g. POSTs to /posts/X/versions)