Web console: make detail archive opening more robust#16071
Merged
gianm merged 1 commit intoapache:masterfrom Mar 8, 2024
Merged
Web console: make detail archive opening more robust#16071gianm merged 1 commit intoapache:masterfrom
gianm merged 1 commit intoapache:masterfrom
Conversation
gianm
approved these changes
Mar 8, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Allow the detail opening dialog to handle cases where not all fields are set on the detail archive (this is possible as the detail archive is generated in a "best effort" approach).
Specifically I came across this issue when opening a detail archive that did not have
statementsStatusset. It crashed.Note: the workaround for now is to manually edit the archive JSON to add
statementsStatus: {}(or whatever is missing) at the top level