Skip to content

Fix <TranslatableInputs> throws error when used with null value#10125

Merged
djhi merged 1 commit intomarmelab:masterfrom
glauff:master
Aug 2, 2024
Merged

Fix <TranslatableInputs> throws error when used with null value#10125
djhi merged 1 commit intomarmelab:masterfrom
glauff:master

Conversation

@glauff
Copy link

@glauff glauff commented Aug 2, 2024

Closes #10107

@fzaninotto fzaninotto changed the title fix #10107 Fix <TranslatableInputs> throws error when used with null value Aug 2, 2024
Copy link
Contributor

@djhi djhi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@djhi djhi added this to the 5.1.1 milestone Aug 2, 2024
@djhi djhi merged commit 477a7f2 into marmelab:master Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

[useTranslatable::getRecordPath] - record with "null" value causes a client error | Edit with <TranslatableInputs>

3 participants