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

Tracking: Cloudflare Images follow-up ideas #4287

Open
ikesau opened this issue Dec 11, 2024 · 0 comments
Open

Tracking: Cloudflare Images follow-up ideas #4287

ikesau opened this issue Dec 11, 2024 · 0 comments
Labels

Comments

@ikesau
Copy link
Member

ikesau commented Dec 11, 2024

A grab bag of potential improvements we'd like to make to cloudflare images, for posterity, while the work is fresh in my mind:

  • Better error handling (or better error handling throughout the admin, more generally)
    • The blunt JSON error responses are a little user unfriendly. The UX could be improved
  • Write operations in prod only
    • Either just changing the staging key, or accompanied with a more comprehensive update to the admin UI that displays a message when in a staging / local environment: "write operations must be performed in prod"
  • A script to check for dangling images
    • Especially if we continue to allow write operations in staging/locally, we'll end up with random images in the Cloudflare Images storage that prod isn't aware of. It'd be nice to periodically check for these so we can prune them.
  • Tags for images
    • Could enable a gallery of images feature? Search? 🤷
@danyx23 danyx23 changed the title Cloudflare Images follow-up ideas Tracking: Cloudflare Images follow-up ideas Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants