fix: regex characters in terms shouldn't block submission

Browse Source

Entering an IP address (e.g. 192.168.1.1) or any term with regex
metacharacters made the form invalid because the "regex characters
detected" hint was wired up via $setValidity('terms', 'regex', false).
The text in the UI labels it as a warning, but the form treated it as
an error and refused to save.

Track the warning as a plain $scope flag and show it via ng-show on
that flag, so the form stays valid (#430).

...

This commit is contained in:

tdurieux

2026-05-04 10:58:17 +02:00

parent 3f095f0734

commit c8fc561dac

3 changed files with 8 additions and 7 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

public/script/bundle.min.js

Vendored

+1 -1

File diff suppressed because one or more lines are too long