-
Notifications
You must be signed in to change notification settings - Fork 208
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) Resolve some errors that appear when an app has empty routes #742
Conversation
68a889f
to
5250860
Compare
Size Change: +22 B (0%) Total Size: 2.13 MB
ℹ️ View Unchanged
|
We swallow the error because a more verbose and useful error happens later? |
@brandones In this particular case, we should actually throw a better and more useful error before we get to this point, i.e., during the assemble command. However, the reason for not throwing an error here is that it’s not in response to a user action; in the loop I’ve added the catch to, we’re trying to pre-cache the container scripts for apps the user hasn’t loaded yet to speed things up when they load them. At the point where the user would perform an action that would require the script, they would still get basically the same error. |
Sorry about the long turnaround; LGTM |
Requirements
For changes to apps
If applicable
Summary
In one of the recent releases, the form builder would fail to load because a
publish
step wasn't properly defined, causing an empty entry in theroute.registry.json
. This PR at least prevents that specific set of circumstances from happening by ensuring that:routes.registry.json
file if theroutes.json
file existsScreenshots
Related Issue
Other