Skip to content

chore: normalize CRLF to LF in bug reports #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ako merged 1 commit into from
Mar 25, 2026
+1,256 −1,256
Merged

chore: normalize CRLF to LF in bug reports #26

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
242 changes: 121 additions & 121 deletions docs/12-bug-reports/BUG_REPORT_mxcli_cross_module_entity_parameter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,121 +1,121 @@
# Bug Report: mxcli fails to create microflow with cross-module entity parameter
## Summary
When creating a microflow with a parameter whose type is an entity from a different module (e.g., `FeedbackModule.Feedback` in a microflow in `MyFirstModule`), mxcli fails with a misleading error message.
## Environment
- **mxcli version**: Current (as of 2026-01-19)
- **Mendix version**: 11.6.0
- **Platform**: macOS (Darwin 25.2.0)
## Steps to Reproduce
1. Connect to a Mendix project:
```bash
./mxcli -p MesDemoApp.mpr
```
2. Try to create a microflow with a cross-module entity parameter:
```sql
CREATE MICROFLOW MyFirstModule.TestMicroflow (
$Feedback: FeedbackModule.Feedback
)
RETURNS Boolean AS $IsValid
BEGIN
DECLARE $IsValid Boolean = true;
RETURN $IsValid;
END;
/
```
## Expected Behavior
The microflow should be created with:
- Parameter `$Feedback` of type `FeedbackModule.Feedback`
- Return type `Boolean`
## Actual Behavior
The command fails with the error:
```
Error: entity '.FeedbackModule' not found for parameter 'Feedback'
```
Additionally, parser warnings are shown:
```
line 2:27 mismatched input '.' expecting ')'
```
### Analysis
The error message `entity '.FeedbackModule' not found` suggests the parser is incorrectly splitting the qualified entity name `FeedbackModule.Feedback`:
- It appears to interpret `FeedbackModule` as `.FeedbackModule` (with a leading dot)
- The entity name `Feedback` is being parsed separately
The parser seems to expect the parameter type to end at the module name, treating the `.` as an unexpected token.
## Workaround Attempts
### Attempt 1: Unqualified entity name
```sql
$Feedback: Feedback
```
**Result**: Microflow is created, but parameter type becomes `Void` instead of `FeedbackModule.Feedback`.
### Attempt 2: Single-line command
```bash
./mxcli -p MesDemoApp.mpr -c "CREATE MICROFLOW MyFirstModule.TestParam(\$Feedback: FeedbackModule.Feedback) RETURNS Boolean AS \$IsValid BEGIN DECLARE \$IsValid Boolean = true; RETURN \$IsValid; END; /"
```
**Result**: Same error - `entity '.FeedbackModule' not found`
### Attempt 3: Script file execution
```bash
./mxcli -p MesDemoApp.mpr -c "EXECUTE SCRIPT '/tmp/test.mdl'"
```
**Result**: Same error
## Evidence
The `mxcli check` command reports syntax as valid:
```
Checking syntax: /tmp/val_feedback_simple.mdl
✓ Syntax OK (1 statements)
```
But execution still fails, indicating a disconnect between the syntax checker and the executor.
## Comparison with Working Cases
Creating a microflow **without** entity parameters works fine:
```sql
CREATE MICROFLOW MyFirstModule.TestMicroflow()
RETURNS Boolean AS $IsValid
BEGIN
DECLARE $IsValid Boolean = true;
RETURN $IsValid;
END;
/
```
**Result**: `Created microflow: MyFirstModule.TestMicroflow`
## Impact
This bug prevents using mxcli to create microflows that:
- Accept entity parameters from other modules
- Are common patterns like validation microflows (VAL_*) in custom modules that validate Marketplace module entities
## Suggested Fix
The parameter type parser should correctly handle fully qualified entity names in the format `Module.Entity`. The `.` should be recognized as a namespace separator, not treated as an unexpected token.
## Related
The skill documentation in `.claude/skills/write-microflows.md` shows the syntax:
```mdl
-- Entity types
$Customer: Module.Entity
```
This confirms the intended syntax supports qualified entity names.
# Bug Report: mxcli fails to create microflow with cross-module entity parameter

## Summary

When creating a microflow with a parameter whose type is an entity from a different module (e.g., `FeedbackModule.Feedback` in a microflow in `MyFirstModule`), mxcli fails with a misleading error message.

## Environment

- **mxcli version**: Current (as of 2026-01-19)
- **Mendix version**: 11.6.0
- **Platform**: macOS (Darwin 25.2.0)

## Steps to Reproduce

1. Connect to a Mendix project:
```bash
./mxcli -p MesDemoApp.mpr
```

2. Try to create a microflow with a cross-module entity parameter:
```sql
CREATE MICROFLOW MyFirstModule.TestMicroflow (
$Feedback: FeedbackModule.Feedback
)
RETURNS Boolean AS $IsValid
BEGIN
DECLARE $IsValid Boolean = true;
RETURN $IsValid;
END;
/
```

## Expected Behavior

The microflow should be created with:
- Parameter `$Feedback` of type `FeedbackModule.Feedback`
- Return type `Boolean`

## Actual Behavior

The command fails with the error:
```
Error: entity '.FeedbackModule' not found for parameter 'Feedback'
```

Additionally, parser warnings are shown:
```
line 2:27 mismatched input '.' expecting ')'
```

### Analysis

The error message `entity '.FeedbackModule' not found` suggests the parser is incorrectly splitting the qualified entity name `FeedbackModule.Feedback`:
- It appears to interpret `FeedbackModule` as `.FeedbackModule` (with a leading dot)
- The entity name `Feedback` is being parsed separately

The parser seems to expect the parameter type to end at the module name, treating the `.` as an unexpected token.

## Workaround Attempts

### Attempt 1: Unqualified entity name
```sql
$Feedback: Feedback
```
**Result**: Microflow is created, but parameter type becomes `Void` instead of `FeedbackModule.Feedback`.

### Attempt 2: Single-line command
```bash
./mxcli -p MesDemoApp.mpr -c "CREATE MICROFLOW MyFirstModule.TestParam(\$Feedback: FeedbackModule.Feedback) RETURNS Boolean AS \$IsValid BEGIN DECLARE \$IsValid Boolean = true; RETURN \$IsValid; END; /"
```
**Result**: Same error - `entity '.FeedbackModule' not found`

### Attempt 3: Script file execution
```bash
./mxcli -p MesDemoApp.mpr -c "EXECUTE SCRIPT '/tmp/test.mdl'"
```
**Result**: Same error

## Evidence

The `mxcli check` command reports syntax as valid:
```
Checking syntax: /tmp/val_feedback_simple.mdl
✓ Syntax OK (1 statements)
```

But execution still fails, indicating a disconnect between the syntax checker and the executor.

## Comparison with Working Cases

Creating a microflow **without** entity parameters works fine:
```sql
CREATE MICROFLOW MyFirstModule.TestMicroflow()
RETURNS Boolean AS $IsValid
BEGIN
DECLARE $IsValid Boolean = true;
RETURN $IsValid;
END;
/
```
**Result**: `Created microflow: MyFirstModule.TestMicroflow`

## Impact

This bug prevents using mxcli to create microflows that:
- Accept entity parameters from other modules
- Are common patterns like validation microflows (VAL_*) in custom modules that validate Marketplace module entities

## Suggested Fix

The parameter type parser should correctly handle fully qualified entity names in the format `Module.Entity`. The `.` should be recognized as a namespace separator, not treated as an unexpected token.

## Related

The skill documentation in `.claude/skills/write-microflows.md` shows the syntax:
```mdl
-- Entity types
$Customer: Module.Entity
```

This confirms the intended syntax supports qualified entity names.
Loading
Loading