lwc-development

To ensure Lightning Web Components use standard Salesforce UI elements, replace generic HTML tags with platform-native lightning- namespace components like lightning-input. This enforces proper SLDS styling, validation, and adherence to official architecture.

Common LWC development anti-patterns include using standard HTML tags instead of lightning- namespace components and utilizing ternary operators directly within HTML templates. Avoiding these ensures proper reactive data binding and Salesforce styling.

Using standard HTML tags instead of SLDS components in Salesforce web components is strongly discouraged. Replacing them with lightning- namespace components guarantees native platform styling, built-in validation, and adherence to Salesforce architecture.

To review existing LWC code for Salesforce best practices, analyze the component selection to verify the use of lightning- namespace elements, proper SLDS styling, and correct reactive data binding instead of anti-patterns like template ternary operators.

Custom Lightning components lack proper Salesforce styling when generic HTML tags are used instead of standard lightning- namespace components. Implementing native SLDS components ensures the UI automatically matches platform design standards.

You need to use lightning- namespace components in LWC whenever creating, modifying, or debugging UI elements like user registration forms. This requirement satisfies SLDS styling rules, reactive data binding needs, and official component architecture standards.