Merge branch 'master' into add_mantine_theme

.github/CODEOWNERS

@@ -1 +1 @@
-* @radekmie @wadamek65
+* @wadamek65 @kestarumper

.github/workflows/CI.yml

@@ -1,5 +1,6 @@
 name: CI
 on:
+  workflow_dispatch:
   pull_request:
   push:
     branches:

docs/uth-autofield-algorithm.md

@@ -46,15 +46,15 @@ const AutoField = createAutoField(props => {
 
 ## Overriding `AutoField`
 
-To make it possible, all `AutoFields` created with the `createAutoField` are configurable. To adjust the components, use the React context available in `AutoField.componentDetectorContext`. You can use it as often as needed - in most apps once will be enough. Example:
+If you want to alter the default behavior of `AutoField` and render a different component based on the props, you can do it using the React context available in `AutoField.componentDetectorContext`. You can use it as often as needed - once will be enough in most apps. Example:
 
 ```tsx
 <AutoField.componentDetectorContext.Provider value={(props, uniforms) => /* ... */}>
   <Application />
 </AutoField.componentDetectorContext.Provider>
 ```
 
-If you want to add an exception and then fallback to the existing algorithm, use `AutoField.defaultComponentDetector`. Example:
+If you want to change the detector only partially, i.e., to render one additional field, and in other cases, use the default algorithm as a fallback, return `AutoField.defaultComponentDetector`. Example:
 
 ```tsx
 <AutoField.componentDetectorContext.Provider

packages/uniforms-antd/__tests__/index.ts

@@ -47,7 +47,10 @@ describe('@RTL', () => {
   suites.testListDelField(theme.ListDelField);
   suites.testListField(theme.ListField, {
     getListAddField: screen => screen.getByRole('img', { name: 'plus-square' }),
+    testTooltip: true,
+    testStyle: true,
   });
+  suites.testListItemField(theme.ListItemField);
   suites.testLongTextField(theme.LongTextField);
   // FIXME: AntD number input doesn't work with new RTL test implementation
   // suites.testNumField(antd.NumField);