Fix null category error when loading from lastrun.json#4644
Closed
GabiNun2 wants to merge 1 commit into
Closed
Conversation
Add default 'Uncategorized' value for Category field when it's missing or null, preventing MethodInvocationException and InvalidOperation errors that occurred when entries from lastrun.json lacked a Category property. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Type of Change
Description
Fixes a null reference error that occurs when loading data from
lastrun.json. The issue happens because entries fromlastrun.jsondon't have aCategoryfield, causingContainsKey()and hashtable indexing operations to fail withMethodInvocationExceptionandInvalidOperationerrors.The fix adds a default value of
"Uncategorized"for the Category field when it's missing or null, consistent with how the Panel field already defaults to"0". This ensures all entries have valid keys for hashtable operations.