Skip to content

Fix item creation failing when a Yes/No field has a non boolean default value - #1293

Open
Lainow wants to merge 1 commit into
11.0/bugfixesfrom
fix/yesno-default-value
Open

Lainow wants to merge 1 commit into
11.0/bugfixesfrom
fix/yesno-default-value

Conversation

@Lainow

@Lainow Lainow commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Checklist before requesting a review

Please delete options that are not relevant.

  • I have performed a self-review of my code.
  • I have added tests (when available) that prove my fix is effective or that my feature works.
  • I have updated the CHANGELOG with a short functional description of the fix or new feature.
  • This change requires a documentation update.

Description

  • It fixes !46805
  • Here is a brief description of what this PR does

Yes/No default values were typed as free text (e.g. Non). Since #1254 applies default values on creation, this breaks item creation on strict SQL mode:

Incorrect integer value: 'Non' for column ...

  • Normalize Yes/No default value to 0/1 (getter, add/update, migration)
  • Use a Yes/No dropdown to configure the default value
  • Add ContainerTest::testYesNoDefaultValueIsNormalized

Screenshots (if appropriate):

@Lainow Lainow self-assigned this Oct 8, 2026
@Lainow
Lainow requested review from MyvTsv and RomainLvr October 8, 2026 08:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant