feature/validation_error_placement

CHANGELOG.md

@@ -1,5 +1,11 @@
 ### Unreleased
 
+- added option `max_depth` used to specify the maximum depth of level's schema that have to be rendered
+- added option `use_default_values` used to specify if default values based on the "type" of the property have to be used
+- when `use_default_values` is false, number and integer fields have undefined value when input is empty
+- when `use_default_values` is false, string fields have undefined value at the beginning. After that user edit the field, empty input is threated as an empty string
+- added option `validation_error_placement` to change position of errors logs under each field 
+
 ### 2.5.1
 
 - Fix for #837 and chekboxes not displaying error messages #843
@@ -12,10 +18,6 @@
 
 ### 2.4.0
 
-- added option `max_depth` used to specify the maximum depth of level's schema that have to be rendered
-- added option `use_default_values` used to specify if default values based on the "type" of the property have to be used
-- when `use_default_values` is false, number and integer fields have undefined value when input is empty
-- when `use_default_values` is false, string fields have undefined value at the beginning. After that user edit the field, empty input is threated as an empty string
 - Fixed using multiple dependencies for an editor. Fix #703
 - Evaluate all dependencies for an editor to determine visibility
 - Fixed meta-schema usage

README.md

@@ -286,6 +286,11 @@ Here are all the available options:
     <td>If true default values based on the "type" of the property will be used</td>
     <td><code>true</code></td>
   </tr>
+  <tr>
+    <td>validation_error_placement</td>
+    <td>Change position where errors are shown. Values are oneOf['grouped', 'below_field']</td>
+    <td><code>grouped</code></td>
+  </tr>
   </tbody>
 </table>