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

I deleted a jpeg and now the whole app crashes #14

Open
andressaroberts opened this issue Aug 23, 2023 · 5 comments
Open

I deleted a jpeg and now the whole app crashes #14

andressaroberts opened this issue Aug 23, 2023 · 5 comments
Labels

Comments

@andressaroberts
Copy link
Contributor

How to reproduce

  1. Put an image on the screen.
  2. Delete it from the media manager.

image

Describe the bug

I deleted a jpeg and now my whole app crashes. If you delete an image, worst that should happen is maybe it doesn't show up or a warning. We can't have the whole app crash over this.

Expected behavior

No response

Operating System

Chrome 112 (macOS Catalina)

Clutch Version

No response

Other

No response

@diegomedina248
Copy link
Contributor

@andressaroberts does the app crash, or just the frame when it's being used.

@magalhas @AndrePessoa this feels more like a feature to be discussed. Ideally, if you try to remove an asset that's being used, we should alert the user first, and if they want to carry with the deletion, I guess we should remove the reference everywhere.

@magalhas
Copy link
Collaborator

magalhas commented Sep 11, 2023

Well if the asset is being imported from a source file it is hard to know it is being used unless we have some kind of static code analysis in place which is way too big of a feature to be considered right now. Did you had something else in mind?

@AndrePessoa
Copy link

@diegomedina248 , I like your suggestion. As we decide to split the "Clutch way" and the "code way", I agree that we should have this polished UX on the UI, alerting about the use impact of removing (an alert modal) and removing all references of it on the instances. The @magalhas case is pretty possible, but if someone is using the code approach, Next's code-driven alert interface seems good to me:
. using UI to use, use UI to delete, use UI to understand the effects = we should try to resolve
. using code to use = we should show the error code console to any error

@diegomedina248
Copy link
Contributor

Yeah, exactly, those two different paths.
I think we can leave the error for now if you used the asset in code, though in the future would be nice to detect.

Both solutions though seem more like a feature, do we want to address either at this point? And if not, what should we do now regarding this issue?

@magalhas
Copy link
Collaborator

I'd go ahead and create a ticket for the new feature and maybe work on it and mark this one as depending on it.

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

4 participants