Pivot away from SanityLive for all data fetching apart from for visual editing #72
Description
Is your enhancement related to a problem? Please describe.
Sanity previously recommended using their LiveClient for all data fetching concerns, however due to the nature of the SSE architecture, this approach can increase hosting costs significantly.
Currently in Ignite we're using this approach.
A fetch wrapper will need to be built which takes in the draftMode flag, this can then be used to flip the client type returned, allowing for instant live updates when visual editing, but defaulting to the HTTP fetch client for all other fetching.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
- I agree to follow this project's Code of Conduct