sf-lwc-development

Use @wire for reads that should be cached and automatically refreshed, such as getRecord or a cacheable=true Apex method. Use imperative Apex for writes, user-triggered actions, and any method that performs DML, since cacheable methods cannot write.

Set isExposed to true in the component's js-meta.xml and add the appropriate target such as lightning__RecordPage or lightning__FlowScreen. Use targetConfigs to declare editable properties, restrict objects, or set form factors.

Mutating a property of an untracked object does not trigger a rerender because the field reference never changed. Reassign the field with a new object or array using spread syntax, or use @track only when in-place mutation is unavoidable.

Call notifyRecordUpdateAvailable with the affected record ids after the imperative Apex write resolves, so Lightning Data Service refreshes dependent wires. For Apex wires specifically, call refreshApex with the provisioned wire result.

Use CustomEvent with default non-bubbling options for child-to-parent communication. Use Lightning Message Service with MessageContext for sibling or cross-DOM communication, including Aura and Visualforce, and always unsubscribe in disconnectedCallback.

No, a cacheable Apex method cannot perform DML and is the only shape @wire accepts. Split the logic into a cacheable read method and a separate non-cacheable @AuraEnabled method for the write.