Skip to content

Add error details to system#31

Closed
neilmcclelland wants to merge 1 commit intomainfrom
feature/KMS20-4043-add-error-details-to-system
Closed

Add error details to system#31
neilmcclelland wants to merge 1 commit intomainfrom
feature/KMS20-4043-add-error-details-to-system

Conversation

@neilmcclelland
Copy link
Copy Markdown
Contributor

Fixes #30

@neilmcclelland neilmcclelland self-assigned this Mar 3, 2026
Copy link
Copy Markdown
Contributor

@Ayurshi-Singh Ayurshi-Singh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good overall.

Comment thread webapp/common/Types.ts
status: SystemStatus
keyConfigurationName: string
keyConfigurationID: string
Metadata?: SystemMetadata
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it Metadata and not metadata?

</ObjectPageSection>
<ObjectPageSection titleUppercase="false" id="systemsObjectPageSectionError"
title="{i18n>errorDetails}"
visible="{= ${oneWay>/selectedSystem/status} === 'FAILED'}">
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we move this to the formatter function, as we decided we will avoid string based checks directly in xm because we can't use enums or coasts in xml. If this is added to the formatter, a test can also be added.

@neilmcclelland
Copy link
Copy Markdown
Contributor Author

closing due to branch name

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.

feature: Add error details to failed system

2 participants