- last update
over 1 year ago 4 fail The last submitted patch, 2: fix_prlp_settings_password_required_variable_type-3268419.patch, failed testing. View results →
- First commit to issue fork.
- Merge request !11Issue#3268419: Resolve test cases that failed and move the code to MR. → (Merged) created by Unnamed author
- last update
over 1 year ago 6 pass - Status changed to Needs review
over 1 year ago 1:04pm 22 May 2023 - 🇮🇳India bharath-kondeti Hyderabad
Raised an MR with updated changes. Please review
- Status changed to RTBC
over 1 year ago 6:54am 23 May 2023 Reviewed MR "Issue#3268419: Resolve test cases that failed and move the code to MR".
The error is resolved.- First commit to issue fork.
-
bharath-kondeti →
authored 58dcc249 on 8.x-1.x
Issue#3268419: Resolve test cases that failed and move the code to MR.
-
bharath-kondeti →
authored 58dcc249 on 8.x-1.x
- First commit to issue fork.
- Merge request !22[#3268419] Fix prlp.settings:password_required variable type → (Open) created by elc
- 🇸🇮Slovenia KlemenDEV
Does lack of this patch in 2.0.x make this module not usable in this release branch, or it still works and is this just a warning?
- 🇦🇺Australia elc
The module will still continue to function, however it will continue to swap between an integer value interpreted as a boolean value, and a true boolean value for this config item.
It's a boolean in the form, should be a boolean because it's a checkbox and true/false, and currently preventing the full validation of the module configuration against the schema.
The point of having the config and schema matched up is to eventually turn on config schema enforcement and validation so that config (simple and entity) and entities can be validated at the entity level instead of a form, allowing for API updates to entities without bypassing all of the validation.