Skip to content

fix(interpreter): add Map case to objectTypeToEZ function#955

Merged
SchoolyB merged 1 commit intobugfixes/1-9-2026from
fix/945-map-type-leak
Jan 8, 2026
Merged

fix(interpreter): add Map case to objectTypeToEZ function#955
SchoolyB merged 1 commit intobugfixes/1-9-2026from
fix/945-map-type-leak

Conversation

@SchoolyB
Copy link
Copy Markdown
Owner

@SchoolyB SchoolyB commented Jan 8, 2026

Summary

  • Added missing *Map case to objectTypeToEZ function
  • Error messages now show map[keyType:valueType] instead of MAP

Before

error[E5012]: return type mismatch: expected map[string:string], got MAP

After

error[E3012]: return type mismatch: expected string, got map[string:string]

Test plan

  • Verified error messages show proper map type format
  • All existing tests pass

Fixes #945

The objectTypeToEZ function was missing a case for *Map, causing
the internal type name "MAP" to leak in error messages instead of
showing the proper "map[keyType:valueType]" format.

Fixes #945
@SchoolyB SchoolyB merged commit 8ac5396 into bugfixes/1-9-2026 Jan 8, 2026
2 checks passed
@SchoolyB SchoolyB deleted the fix/945-map-type-leak branch January 8, 2026 19:31
SchoolyB added a commit that referenced this pull request Apr 3, 2026
The objectTypeToEZ function was missing a case for *Map, causing
the internal type name "MAP" to leak in error messages instead of
showing the proper "map[keyType:valueType]" format.

Fixes #945
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.

Bug: objectTypeToEZ missing Map case, causing "MAP" to leak in error messages (regression from #904)

1 participant