The naming standards for some blueprints and their properties are inconsistent. If we look at something like the ADO Integration and the blueprints.

* ADO Project - BP Identifier: "project"

* ADO User - BP Identifier: "azureDevOpsUser"

Additionally if take the ADO User BP identifier, it uses camel case whereas auto generated properties will utilise snake case.

As a builder, by improving the naming standards/conventions, this would help remove ambiguity around things like mapping relations, utilising properties in widgets etc.