Skip to content

fix(dashboard): Ensure nullable numeric fields default to null#2

Open
grolmus wants to merge 1 commit intomasterfrom
fix/oss-353-nullable-usage-limit
Open

fix(dashboard): Ensure nullable numeric fields default to null#2
grolmus wants to merge 1 commit intomasterfrom
fix/oss-353-nullable-usage-limit

Conversation

@grolmus
Copy link
Owner

@grolmus grolmus commented Feb 25, 2026

Summary

  • Nullable Int, Float, Money, and DateTime fields now correctly default to null instead of 0
  • Fixes promotion usageLimit and perCustomerUsageLimit fields defaulting to 0 when creating new promotions

Test plan

  • Unit tests pass
  • Manual test: Create new promotion, verify usageLimit fields are empty (null) not 0

Fixes vendurehq#4328

Nullable Int, Float, Money, and DateTime fields now correctly default
to null instead of falling through to the default case. This fixes
promotion usageLimit and perCustomerUsageLimit fields defaulting to 0.

Fixes vendurehq#4328
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant