fix: content edit

[IkbelTalebHssan]

Motivation

We need to ensure that content["dynamicFields"] is defined before trying to access its properties.

Fixes (issue)

Type of change:

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added unit tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[marrouchi]

The content type "add" form, needs to includes the dynamic fields so that the user doesn't have to edit again to configure those.

API side, we need to add a default value.

[IkbelTalebHssan]

The content type "add" form, needs to includes the dynamic fields so that the user doesn't have to edit again to configure those.

API side, we need to add a default value.

Thank you for the review 🙏
Updates are done ✔️

[yassinedorbozgithub]

Hi @IkbelTalebHssan, i have noticed that the input helperText attribute is accidentally removed

Suggested change

	{...register("name", {
	required: t("message.name_is_required"),
	})}
	{...register("name", {
	required: t("message.name_is_required"),
	})}
	helperText={errors.name ? errors.name.message : null}

[IkbelTalebHssan]

accidentally removed

Thank you @yassinedorbozgithub for the review 🙏
Fixed ✔️

[marrouchi]

As a general rule, useEffect() should be place at the end, before the "return"

[marrouchi]

Suggested change

	createContentType({ ...params, name: params.name || "" });
	createContentType({ ...params, name: params.name || "" });

The content type "name" attribute should not be empty. In which case are getting it empty?