You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we want to use cloudinary image urls only, since they offer more powerful transformations, and because our frontend is already configured for cloudinary!
However, in the sanity payloads only sanity image urls are included. I read here, how to reconstruct the full cloudinary URL. However, for that an additional request to the asset is required, and overall not very handy if we only want to use cloudinary. Is it somehow possible to directly return the cloudinary url in the payload, or is there any other way to easily access the cloudinary url?
The text was updated successfully, but these errors were encountered:
@ontoneio Thanks 👌 In the end we modified the plugin a bit to store the full cloudinary path on the asset.
However, the extra request does not seem to be avoidable unfortunately with how images work in Sanity, since they are references and only the ID is accessible without extra request to the full asset. So now we are doing that extra request, which is not so bad since our website is static.
Hi guys,
we want to use cloudinary image urls only, since they offer more powerful transformations, and because our frontend is already configured for cloudinary!
However, in the sanity payloads only sanity image urls are included. I read here, how to reconstruct the full cloudinary URL. However, for that an additional request to the asset is required, and overall not very handy if we only want to use cloudinary. Is it somehow possible to directly return the cloudinary url in the payload, or is there any other way to easily access the cloudinary url?
The text was updated successfully, but these errors were encountered: