Skip to content

fix: default recurrenceUnit on team notification - #35

Merged
Eduardojvr merged 1 commit into
homologacaofrom
fix/team-notification-recurrence-unit-default-homolog
Oct 15, 2026
Merged

Eduardojvr merged 1 commit into
homologacaofrom
fix/team-notification-recurrence-unit-default-homolog

Conversation

@Eduardojvr

Copy link
Copy Markdown
Collaborator

Summary

Same fix as #34, targeting homologacao directly since it's ahead of dev and already has the team notification feature.

  • recurrenceUnit has an enum, and the generic enum-validation mixin treats any enum field as required whenever its value is undefined — so creating a non-recurring team notification (where recurrenceUnit is intentionally omitted) failed with "recurrenceUnit is blank".
  • Added a default: "h" the same way severity already has one, so the field is never left undefined.

Test plan

  • Create a non-recurring team notification (recurring off) and confirm it saves without the blank-enum error.
  • Create a recurring one and confirm recurrenceUnit still saves/behaves as selected.

…validation error

The enum mixin treats any enum field as required when undefined, so
creating a non-recurring notification (recurrenceUnit omitted) failed
with "recurrenceUnit is blank". Give it the same kind of default the
severity field already has.
@Eduardojvr
Eduardojvr merged commit e9de11d into homologacao Oct 15, 2026
1 check passed
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