Hi guys, is it normal that I can't whitelist a chrome extension to avoid CORS when calling the sanity client?

3 replies

Last updated: Jan 23, 2021

Jan 22, 2021, 10:10 PM

is there a way to manually set CORS?

Jan 23, 2021, 2:48 PM

ehm, I fixed it by bypassing the UI error validation... this should be a legit usecase.

Jan 23, 2021, 3:02 PM

Thanks for reporting! I've sent a pull request to improve the validation in the new management console preview 🙂

Jan 23, 2021, 9:38 PM

Sanity.io: Get the most out of your content

Sanity.io is a platform to build websites and applications. It comes with great APIs that let you treat content like data. Give your team exactly what they need to edit and publish their content with the customizable Sanity Studio. Get real-time collaboration out of the box. Sanity.io comes with a hosted datastore for JSON documents, query languages like GROQ and GraphQL, CDNs, on-demand asset transformations, presentation agnostic rich text, plugins, and much more.

Don't compromise on developer experience. Join thousands of developers and trusted companies and power your content with Sanity.io. Free to get started, pay-as-you-go on all plans.