Update UIHealthReport.cs #911
Merged
Conversation
This file contains 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
Fix null Entries in UIHealthReport
sungam3r
approved these changes
Feb 18, 2022
|
Thank you for your collaboration @mipa87 . This change has been published on UI packages 6.0.3 |
This was referenced Feb 20, 2022
Closed
6 tasks
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix null Entries in UIHealthReport
What this PR does / why we need it:
Fixes the NullReferenceException when accessing null Entries in UIHealthReport. For example in HealthReportExtensions.
Which issue(s) this PR fixes:
Please reference the issue this PR will close: #[issue number]Special notes for your reviewer:
Occurs when HealthCheckReportCollector.GetHealthReport successfully deserializes the response, but in the requested URI is another API, which provide only "status" property and "entries" are omitted:
{"title":"NotFound","status":404,"detail":"NotFound"}Does this PR introduce a user-facing change?:
No
Please make sure you've completed the relevant tasks for this PR, out of the following list: