-
Notifications
You must be signed in to change notification settings - Fork 11
Fixed an issue where an error while fetching schemas caused the XDM Object data element to be unusable #527
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
base: main
Are you sure you want to change the base?
Conversation
…bject data element to be unusable
| initialValues.schema = schemasFirstPage[0]; | ||
| } | ||
| } catch { | ||
| context.schemasFirstPage = []; |
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.
In both catch statements, I would feel more comfortable if we had some kind of logging or alert, just in case some issue pops up. Let me know what you think.
|
Updates from my commit:
|
…ion has a schema/sandbox but cannot load it
jonsnyder
left a comment
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.
Amazing! I love the detailed tests.
| if (e.name === "AbortError") { | ||
| throw e; | ||
| } | ||
| throw e; |
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.
It seems this catch block could be removed as it always throws.
Description
Related Issue
Motivation and Context
Screenshots (if appropriate):
Spencer: Alert and placeholder text for when unable to retrieve the sandbox/schema from a saved configuration
Types of changes
Checklist: