Defect: Empty string enum values fail as Unknown keyword

[eviltester]

Summary

enum("","A") and related empty string enum values fail as Unknown keyword: enum, while whitespace enum values and literal("") work.

Reference

• Parent testing issue: Testing: Issue 295 / PR 305 deployed exploratory review #306
• Story: Schema UI Param editor should support enum values #295
• PR: Add enum picker editing for schema params #305
• Full defect report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260702/issue-295-001/defects/defect-002-empty-string-enum-values-fail-as-unknown-keyword.md
• Main testing report: https://github.com/eviltester/anywaydata-ai-testing/blob/main/docs/testing/20260702/issue-295-001/issue-295-test-report.md

Supporting evidence

Notes

Evidence attached here is text and screenshots only. Local-only support logs and videos were not attached.

[eviltester]

Implemented the enum empty-string handling in commit 4601c14 on branch 295-enum-picker.

What changed:

• Explicit empty string enum values are now accepted and preserved, e.g. enum("","A"), datatype.enum("", "A"), datatype.enum(values=["", "A"]), and datatype.enum(values="").
• Accidental empty CSV slots are still rejected before generation when "" is not part of the defined enum set, e.g. active,,pending or datatype.enum(csv="active,,pending").
• The parser/compiler keeps these cases on the enum/domain validation path instead of falling through to Unknown keyword: enum.
• Schema row editing preserves invalid in-progress enum text so validation can be displayed without interrupting editing.

Validation completed locally:

• Targeted enum/parser/schema tests
• pnpm run verify:ui
• pnpm run verify:local