Improving readability of user defined rules - #894
Open
hitman1711 wants to merge 2 commits into
Open
Conversation
hitman1711
marked this pull request as ready for review
July 5, 2026 18:00
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
1 participant
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.
Motivation
User-entered IP range such as: 1.2.3.4 - 23.3.4.6 should remain recognizable as an IP range rule in the UI.
The goal is to make range, CIDR, and wildcard rules easier to understand and manage while preserving compatibility with existing rules and matcher semantics.
Changes
• Added optional endpoint display metadata to Rule.
• Added archive and JSON import/export support for the new optional metadata.
• Added friendly endpoint helper methods for display/type/matcher text.
• Updated Add/Edit Rule behavior to preserve the user-friendly endpoint input.
• Preserved generated wildcard regex as the technical matcher while showing the original wildcard value.
• Updated the rules list connection row to show matcher details in a dedicated detail line.
• Added tooltips for long endpoint and matcher text.
• Rejected reversed IP ranges instead of silently normalizing them.
• Rejected malformed IP range-like input instead of saving it as an exact-match rule.
Related issue
Closes #885