Skip to content

Commit a153f87

Browse files
committed
docs: Fix issue in readme
1 parent 4581bf1 commit a153f87

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -346,14 +346,6 @@ Example:
346346

347347
> `required:` NO | `type:` array
348348
349-
#### JSON fields
350-
351-
This property can accept an array of field names from the type. It is meant to specify the JSON fields on the type so the plugin can better format the field values when calculating the config difference.
352-
353-
###### Key: `jsonFields`
354-
355-
> `required:` NO | `type:` array
356-
357349
#### Components
358350

359351
This property can accept an array of component names from the type. Strapi Components can be included in the export/import process. With "." nested components can also be included in the process.
@@ -364,11 +356,19 @@ customTypes: [{
364356
uid: 'name',
365357
components: ['ParentComponentA', 'ParentComponentA.ChildComponent', 'ParentComponentB']
366358
}],
359+
```
367360

368361
###### Key: `components`
369362

370363
> `required:` NO | `type:` array
371364
365+
#### JSON fields
366+
367+
This property can accept an array of field names from the type. It is meant to specify the JSON fields on the type so the plugin can better format the field values when calculating the config difference.
368+
369+
###### Key: `jsonFields`
370+
371+
> `required:` NO | `type:` array
372372
373373
## 🔍 Naming convention
374374
All the config files written in the sync directory have the same naming convention. It goes as follows:

0 commit comments

Comments
 (0)