Skip to content

[BUG] Silently reject empty enum values instead of storing them (#292) - #744

Merged
antonis96 merged 1 commit into
developfrom
292-dont-allow-empty-enums
Jul 30, 2026
Merged

[BUG] Silently reject empty enum values instead of storing them (#292)#744
antonis96 merged 1 commit into
developfrom
292-dont-allow-empty-enums

Conversation

@antonis96

@antonis96 antonis96 commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

Change(s)

Change Type:

Change Category:

Changelog Entry:

How to Test

Checklist

  • Tests have been added or updated to reflect the changes, or their absence is explicitly explained.
  • Documentation has been added or updated to reflect the changes, or their absence is explicitly explained.
  • A self-review has been conducted checking:
    • No unintended changes have been committed.
    • The changes in isolation seem reasonable.
    • Anything that may be odd or unintuitive is provided with a GitHub comment explaining it (but consider if this should not be a code comment or in the documentation instead).
  • All CI checks pass before pinging a reviewer, or provide an explanation if they do not.
  • The PR title matches the changelog entry's one-line description.

Related Issues

@antonis96 antonis96 linked an issue Jul 30, 2026 that may be closed by this pull request
@antonis96
antonis96 merged commit 42a95b8 into develop Jul 30, 2026
0 of 2 checks passed
@antonis96
antonis96 deleted the 292-dont-allow-empty-enums branch July 30, 2026 10:26
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.

Don't allow empty ("") enums

1 participant