Inconsistent naming Aura controller properties

Naming conventions help drive consistency across the application, which makes source code easier to read and understand.

Suboptimal resource allocation, increased costs, and delayed time-to-market for new features and products.

Is your Salesforce solution affected by Inconsistent naming Aura controller properties?

Clayton detects anti-patterns and offers automated fix advice to kickstart your Well-Architected journey.

How common is this issue?

Data not available

How long do organizations remain exposed before fixing the problem?

Data not available

Easy

Intentional

Readability

Design Standards

Found a mistake?

If you think something is incorrect, missing or misleading please let us know.