Skip to content

Added mention about default values for migrations #2349

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 5, 2024
Merged

Added mention about default values for migrations #2349

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7822457
Added mention about default values for migrations
mnocon Mar 28, 2024
da9fb5d
Applied review suggestion
mnocon Apr 3, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions code_samples/data_migration/examples/create_product_type.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@
- identifier: specification
type: ibexa_product_specification
required: true
translatable: false
translations:
eng-GB:
name: Specification
Expand Down
5 changes: 5 additions & 0 deletions docs/content_management/data_migration/importing_data.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -213,6 +213,11 @@ The following example shows how to create a content type with two Field definiti

The required metadata keys are: `identifier`, `mainTranslation`, `contentTypeGroups` and `translations`.

The default values of Field definition properties mirror the underlying PHP API, for example:

- `translatable` defaults to `true`
- `required` defaults to `false`

``` yaml
[[= include_file('code_samples/data_migration/examples/create_blog_post_ct.yaml') =]]
```
Expand Down