What is best practice around naming lightning components bundles in an org? Concerned as it components are visible across applications which means naming conflicts can occur.
Considering prefixing each lightning component with the application prefix. i.e. if I was building an auditing app called
InternalAudit.app then all my resources would be prefixed by
Am I missing something here or should it be considered best practice to prefix any lightning component with the application parent?
Anyone have a better technique?