There's a well documented best practice on naming conventions:
https://docs.mendix.com/refguide/dev-best-practices/
Studio Pro should support in adhering to this naming convention. It would be much easier for new Mendix developers if the proposed names would match this convention.
When creating an import mapping it's named "Import_mapping" while the convention is "IMM_" - similar when autogenerating it from a message definition.
A new microflow from a REST service is named "PostResource_" while it should be "PRS_"
There's more such examples where the generated name doesn't match the naming convention and you easily start mixing up this default naming with the best practice.
It might even be more usefull if the naming of such items could be customized if someone wants to use his own naming conventions - that would also allow to update the naming convention independently from Studio Pro.
regards, Fabian
So true. It could even be helpful like ACT_[Entity]_[Action] and so on.
I totally agree, Fabian! Improvements like these will make the Mendix ecosystem more consistent, which improves productivity for the whole community.