Skip to content

fix: add OPEN to keyword rule for enum value parsing#174

Open
engalar wants to merge 1 commit intomendixlabs:mainfrom
engalar:fix/open-keyword-in-enum
Open

fix: add OPEN to keyword rule for enum value parsing#174
engalar wants to merge 1 commit intomendixlabs:mainfrom
engalar:fix/open-keyword-in-enum

Conversation

@engalar
Copy link
Copy Markdown
Contributor

@engalar engalar commented Apr 10, 2026

Summary

  • OPEN was a lexer token (used by OPEN USER TASK, OPEN WORKFLOW) but missing from the parser's keyword rule
  • This caused 3-part enum values like Module.ENUM_IssueStatus.Open to fail parsing in CREATE/CHANGE statements within microflow bodies
  • The fix adds OPEN to the keyword alternatives in MDLParser.g4 line 3592

Reproduction

CREATE OR REPLACE MICROFLOW MyModule.Test ()
RETURNS Nothing
BEGIN
  $Issue = CREATE MyModule.OrderIssue (
    IssueNumber = 'TEST',
    Status = MyModule.ENUM_IssueStatus.Open,
    IssueType = MyModule.ENUM_IssueType.DeliveryDelay
  );
END;

Before: line 6:47 mismatched input '.' expecting ')'
After: Syntax OK

Test plan

  • mxcli check passes for enum values with Open (previously reserved keyword)
  • Existing tests still pass
  • OPEN USER TASK and OPEN WORKFLOW syntax unaffected

🤖 Generated with Claude Code

…rectly

OPEN was defined as a lexer token (for OPEN USER TASK, OPEN WORKFLOW)
but missing from the parser's keyword rule, causing 3-part enum values
like Module.ENUM_IssueStatus.Open to fail parsing in CREATE/CHANGE
statements within microflow bodies.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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