Improve hazard type filter logic (#21)#51
Merged
lydiascarf merged 2 commits intordl-0.3from Nov 10, 2025
Merged
Conversation
Enabling hazard type filter should exclude all datasets with a category of exposure and disable the exposure filter in the UI.
matamadio
approved these changes
Nov 10, 2025
matamadio
left a comment
There was a problem hiding this comment.
Thanks, it might not be the final solution to the issue but for now it can work
lydiascarf
added a commit
that referenced
this pull request
Nov 17, 2025
Requires reverting changes from PR #51 Category/Risk Data Type is now a multi-filter, which filters to datasets that have at least one of the selected category filters.
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.
Enabling hazard type filter should exclude all datasets with a category of exposure and disable the exposure filter in the UI. I'm going to handle the refresh issue in a separate PR because it might be a bit more of a refactor. I'll comment about this on the issue.