We have days where we have infrequent changes to our content, so we decided to host a cache that handles the bulk of the content delivery requests to dato’s graphql endpoint. So far this has been working pretty great - we just invalidate the cache whenever an entity is published via a webhook. However we just noticed that the seo settings are not considered an entity
, so changes won’t trigger our webhook. The support has confirmed that there is no way of triggering a webhook if the settings change, so this is the formal feature request for that. Feedback appreciated.
Consider this query:
query PageHome {
webPageHome {
_seoMetaTags {
...seoMetaTagsFields
}
entryTitle
entrySubtitle
}
If we changed the seo settings, this query would return stale data, because there is no way of triggering an invalidation.