[OGUI-1073] Infologger link can get stuck if provided invalid filter parameters#3439
Merged
isaachilly merged 3 commits intodevfrom May 8, 2026
Merged
Conversation
…ms are unparseable Added a try and catch to check if the URL filter params are parseable, if they are not raise a danger notification stating the JSON error message.
isaachilly
added
Frontend
InfoLogger
javascript
Parsing error is engine-specific and CI/CD with Puppeteer uses Chromium by default.
graduta
approved these changes
May 8, 2026
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
2 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.
I have JIRA issue created
This PR adds a try and catch when the parsing of filter params occurs on location change.