Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
cat -n Core/Resgrid.Model/DepartmentNotification.cs | head -300Repository: Resgrid/Core
Length of output: 9712
Use non-throwing parsing in these translation branches.
These guards fix the blank-data case, but lines 97, 126, 155, 217, 246, and 275 still use
int.Parseon any other non-empty value. A legacy or partially corrupted notification row will still throw while rendering the page. Additionally, lines 157, 248, and 277 contain redundant parse calls that should also be made non-throwing.Switch all these branches to
int.TryParsewith the current "Unknown"/"Any" sentinel fallback.Suggested pattern
Apply the same pattern to all instances in both
TranslateBeforeandTranslateCurrentmethods.Also applies to: 120-121, 149-150, 157, 211-212, 240-241, 248, 269-270, 277
🤖 Prompt for AI Agents