Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: dont load entire images to check if they exist #1073

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

mikaelbr
Copy link
Member

To check for where the image is stored, the client actually fetches the image in addition to actually load it as an image. This check I think is only ment to construct an URL with correct metadata, so this is unnecessary. I don't have time to prioritise for a proper fix and avoid this issue properly, but as a temporary measure we can at least avoid loading 5-6 megs of images just to check if they exists.

Again: We shouldn't have it like this, and we should find a proper way to separate shared studio image vs non-shared. But to avoid downloading lots of lots of data that isn't used, we could at least do some temporary workarounds.

Before:
image

After:
Screenshot 2024-12-18 at 10 47 57

Copy link

vercel bot commented Dec 18, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
variant-no ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 18, 2024 9:51am
variant-se-2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 18, 2024 9:51am

@mikaelbr
Copy link
Member Author

This also explains the annoying 404 I've seen when loading the page.. 😅

@mikaelbr mikaelbr merged commit 7f3d050 into v3 Dec 18, 2024
6 checks passed
@mikaelbr mikaelbr deleted the mikael/reduce-loading-images branch December 18, 2024 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants