salesforce-component-standards

Choose based on use case: use @wire(getRecord) for reactive single-record reads, lightning-record-form for standard CRUD forms, wired cacheable Apex for complex queries, imperative Apex for DML or user-triggered actions, and GraphQL wire for multi-object relationships.

Use template expression binding {expression} instead of setting innerHTML with user data, since the framework auto-escapes bound values. Never assign user-controlled values to innerHTML via querySelector.

Always use LWC for new components unless the target context is Aura-only, such as extending force:appPage or using Aura-specific events in legacy managed packages. LWC can be embedded inside Aura components during incremental migration.

Standard controllers enforce FLS for bound fields automatically, but custom controllers do not. You must add explicit Schema.sObjectType checks like isAccessible() and isDeletable() before reading fields or performing DML.

Setting a reactive property inside renderedCallback triggers another render cycle, causing an infinite loop. Always guard renderedCallback with a boolean flag like hasRendered and avoid mutating reactive state there.

Components handling user interaction or Apex data need tests for rendering, Apex wire mocking with emit({data, error}), event dispatch verification, and error-state handling. Use @salesforce/sfdx-lwc-jest mocking utilities for wire adapters and Apex methods.