Bug 41424 - Add Sanitizer(allow_none=True)
Add Sanitizer(allow_none=True)
Product: UCS
Classification: Unclassified
Component: UMC (Generic)
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-2-errata
Assigned To: Florian Best
Dirk Wiesenthal
Depends on:
  Show dependency treegraph
Reported: 2016-06-02 15:21 CEST by Florian Best
Modified: 2016-09-29 17:31 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.046
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:
best: Patch_Available+

patch (1.44 KB, patch)
2016-06-02 15:21 CEST, Florian Best
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Best univentionstaff 2016-06-02 15:21:07 CEST
Created attachment 7715 [details]

The Sanitizer base class should have a parameter 'allow_none' which stops further processing if the value is None.
This is very helpful in combination with e.g. StringSanitizer where one have optional arguments → None or a string.

Patch attached.
Comment 1 Florian Best univentionstaff 2016-06-23 19:53:01 CEST
r70595 | YAML Bug #41424, Bug #41423, Bug #41070

univention-management-console (8.0.28-15):
r70590 | Bug #41424: add allow_none parameter to Sanitizer
Comment 2 Dirk Wiesenthal univentionstaff 2016-07-11 23:04:26 CEST
Code: OK
Comment 3 Janek Walkenhorst univentionstaff 2016-07-21 15:16:19 CEST