Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes linked record and Events > Browse views to account for event outcomes that are blank/NULL. Added a ternary in the impacted views to confirm that a
record['outcome']
exists before attempting to display the translation for that outcome value in the table. Additionally, I confirmed by pulling records out via the API that, when an outcome is not present in a record, the outcome key does not exist (e.g. it's just not there, not it's there but is blank).Related JIRA Ticket or GitHub Issue
Partial fix for: https://archivesspace.atlassian.net/browse/ANW-778
Motivation and Context
An outcome is not a required field for an event record, so the outcome column in the staff UI should not assume that there will always be a value to display.
How Has This Been Tested?
Backend tests passed looked, inspected visually on a local branch.
Screenshots (if appropriate):
Before change:
After change:
Types of changes
Checklist: