Bug #17870
closedSaving an empty matcher for smart class parameter of type boolean saves the value false
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1357049
Description of problem:
'Required' functionality is not working for smart class parameter type 'boolean'.
Version-Release number of selected component (if applicable):
Sat 6.2 snap 19.1 GA
How reproducible:
Always
Steps to Reproduce:
1. Set default value for parameter type 'boolean' to true.
2. Select required checkbox to validate that value shouldnt be blank.
3. Create a matcher with empty/blank value.
4. Attempt to submit it.
Actual results:
The parameter is submitted by setting matcher value to 'false' automatically.
Expected results:
1. The parameter should not be submitted and should throw an error 'Value can't be blank'.
2. Autoset of boolean value to false for matcher should not happen.
Updated by Ori Rabin almost 8 years ago
- Status changed from New to Assigned
- Assignee set to Ori Rabin
- Target version set to 1.15.3
Updated by The Foreman Bot almost 8 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4144 added
Updated by Ori Rabin almost 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset d836a8383f1188f23b6ffbffa1a8fbbf52bef139.
Updated by Dominic Cleal almost 8 years ago
- Translation missing: en.field_release set to 210
Updated by The Foreman Bot over 7 years ago
- Pull request https://github.com/theforeman/foreman/pull/4345 added
Updated by Ori Rabin over 7 years ago
- Related to Bug #18718: Saving a boolean matcher with no value changes the value to false added
Updated by Ori Rabin over 7 years ago
- Pull request deleted (
https://github.com/theforeman/foreman/pull/4345)