Skip to content

Conversation

codeworrior
Copy link
Member

When a managed object class has a module:* name, the names are now correctly split into prefix and base name when calculating the name of the EventParameters and EventType types.

The implementation of the calculations is now shared with the calculation implemented in b6c0fe5.

fullEventTypealiasName,
shortEventTypealiasName,
} = makeEventParametersName(symbol.name, event.name);
const { eventParametersNames, eventTypeAliasNames } =
Copy link
Member

@akudev akudev Oct 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the plural forms are intentional? Seems so, but then again, the function returning the "...Names" is called "make...Name"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, they are intentional. The returned objects contain different "names". But I'm definitely open for better naming proposals.

@akudev
Copy link
Member

akudev commented Oct 10, 2025

I think you anyway have to adapt the test snapshots. Maybe seeing the resulting changes will also help understanding the effects of this fix.

When a managed object class has a module:* name, the names are now
correctly split into prefix and base name when calculating the name
of the EventParameters and EventType types.

The implementation of the calculations is now shared with the
calculation implemented in b6c0fe5.
@codeworrior codeworrior force-pushed the support-module-names-for-events branch from 0ea9810 to 62213b2 Compare October 10, 2025 15:38
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.

2 participants