Skip to content

MvM UpdateNamingConventions#11386

Open
MarkvanMents wants to merge 3 commits into
developmentfrom
MvM-UpdateNamingConventions
Open

MvM UpdateNamingConventions#11386
MarkvanMents wants to merge 3 commits into
developmentfrom
MvM-UpdateNamingConventions

Conversation

@MarkvanMents

@MarkvanMents MarkvanMents commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

Update the naming conventions as suggested in #11028

Mendix advises using names which avoid abbreviations and underscores. Entity names should use PascalCase, for example, **HousekeepingRecord** or **LogEntry**.

{{% alert color="info" %}}
Following these entity naming conventions will prevent issues with naming conflicts between modules and entities. For example, if a module named **Customer** contains an entity named **customer** (note the lower-case "c"), there will be a Java compilation error and the app will not run. Renaming the entity to **Customer** will solve the problem.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I find this unclear - if the module name is capitalized and the entity name is not capitalized why is there a naming conflict. Surely the conflict comes if two things have the same name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants