Update feature list #11
Conversation
Not all categories are directly applicable, e.g. due to GROQ, our REST APIs are much more powerful compared to most RESTful APIs.
|
@kmelve Thanks for your PR can you please provide links to the changed features so that I can confirm that the changes are correct? |
| "Docker Support": "NA", | ||
| "Backup Feature": "No", | ||
| "Backup Feature": "Yes", |
There was a problem hiding this comment.
All changes/patches to content are backed up, also API endpoints for full exports of datasets.
There was a problem hiding this comment.
Where is the backup feature documented? I could not find it in the docs.
| "GDPR Statement": "", | ||
| "GDPR API": "No", | ||
| "Editing Conflict Detection": "", | ||
| "Content Trees": "Yes", |
There was a problem hiding this comment.
Fully customizeable with Structure Builder. https://www.sanity.io/docs/content-studio/structure-builder
There was a problem hiding this comment.
Is this also limited to 20 levels?
| "Nesting of Fields": "Yes", | ||
| "GDPR Statement": "Yes", | ||
| "GDPR API": "Yes", | ||
| "Editing Conflict Detection": "Yes", |
There was a problem hiding this comment.
Backend is real-time, every patch get a revision ID
There was a problem hiding this comment.
What happens when a content is updated with two different requests? Will the second request override the updated data of the first request?
There was a problem hiding this comment.
Everything is transactional, so if the transaction includes the revision id of the document, it will fail if the document has been changed meanwhile (and tell the client). If not, it will update the document.
There was a problem hiding this comment.
@kmelve Very nice. Is this documented somewhere? What is the error code in those cases? 409? 400?
| "Versioning": "Yes", | ||
| "Content Scheduling": "No", | ||
| "Content Scheduling": "Yes", |
There was a problem hiding this comment.
You can use custom access control https://www.sanity.io/docs/data-store/access-control#group-documents and predefined parameters in GROQ (https://www.sanity.io/docs/groq/groq-parameters#predefined-parameters)
There was a problem hiding this comment.
I don't think this applies. Is it possible to schedule the publication of a specific content? Is it possible to define a timeframe in which the content is online?
There was a problem hiding this comment.
Yeah, on any document type you can add a date field (or more). You can then set the access rules to "make this available for a said group (everyone, and/or certain roles) when the date on the document is less than what time is now", and vice-versa if you want to unpublish it.
|
Done @Jotschi! |
|
I have merged the already checked and solved fields. |
Not all categories are directly applicable, e.g. due to GROQ, our REST APIs are much more powerful compared to most RESTful APIs.