-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add error when extract resource build fails #4964
Conversation
Another one for #1255... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel like a .expect() is appropriate here. It should be a fatal error imo as the code is wrong. Also, why did the render app not exist yet? This is a plugin. Did you add it before DefaultPlugins or something? @alice-i-cecile @cart what do you think? Fatal or not?
Definitely fatal; I don't think there's any way to recover from this. The fix is always just "order your plugins better", as much as I hate that. |
Good point. |
baca764
to
496ccef
Compare
Iirc we adopted the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Objective
I had some troubleshooting pain when this happened to me, as the panic only tells you a resource is missing. This PR adds an error when the ExtractResource plugin is added before the render world exists, instead of silently failing.