Skip to content

Conversation

@gweiermann
Copy link

@gweiermann gweiermann commented Jan 20, 2026

What?

Deprecates allowEmpty for mt-number-field, sets its default to true.

Why?

See #1009.

How?

  • Deprecated allowEmpty prop from mt-number-field component and removed it from tests.
  • Added warnings for deprecated allowEmpty prop usage in both true and false cases.
  • Updated default behavior to true.

Testing?

  • Assert that a warning is shown when allowEmpty gets set to true or false.
  • Ensure that no warning is shown when allowEmpty is not set

Anything Else?

Discussion in slack: https://shopware-ag.slack.com/archives/CBAS8D2GH/p1766159096610889

Closes #1009.

- Removed allowEmpty prop from mt-number-field component and its tests.
- Added warnings for deprecated allowEmpty prop usage in both true and false cases.
- Updated default behavior to handle empty values without allowEmpty.
- Adjusted mt-unit-field to remove allowEmpty prop reference.
@vercel
Copy link

vercel bot commented Jan 20, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Review Updated (UTC)
meteor-component-library Ignored Ignored Preview Jan 20, 2026 3:55pm

Request Review

@gweiermann gweiermann changed the title refactor(mt-number-field)!: deprecate allowEmpty prop and make it true by default refactor(component-library)!: deprecate allowEmpty prop and make it true by default Jan 20, 2026
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.

Change behaviour of allowEmpty property in <mt-number-field />

2 participants