Skip to content

Conversation

@jonsnyder
Copy link
Collaborator

@jonsnyder jonsnyder commented Sep 16, 2025

Description

Related Issue

Motivation and Context

Screenshots (if appropriate):

Screenshot 2026-01-14 at 9 31 46 AM

Spencer: Alert and placeholder text for when unable to retrieve the sandbox/schema from a saved configuration

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (non-breaking change which does not add functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA or I'm an Adobe employee.
  • I have made any necessary test changes and all tests pass.
  • I have run the Sandbox successfully.
  • I've updated the schema in extension.json or no changes are necessary.
  • My change requires a change to the documentation.

initialValues.schema = schemasFirstPage[0];
}
} catch {
context.schemasFirstPage = [];
Copy link
Collaborator

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.

@Spencer-Smith
Copy link
Collaborator

Updates from my commit:

  • Added error handling for sandbox and schema selection in XDM Object, Variable data elements, and Update Variable actions
  • Added handling for a few missed response code in the fetchFromReactor
  • Updated handling for schema fetch failures (e.g., 404 when auto-selecting a single schema) to display an inline alert; this allows users to select a different schema, rather than crashing to an error boundary
  • Refactored some component files to separate rendering so that they can be used for integration tests

Copy link
Collaborator Author

@jonsnyder jonsnyder left a 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;
Copy link
Collaborator Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants