Lightning Components Developer Guide

What is the Lightning Component Framework?
Quick Start
Creating Components
Component Names
Create Lightning Components in the Developer Console
Component Markup
Component Namespace
Component Bundles
Component IDs
HTML in Components
CSS in Components
Component Attributes
Component Composition
Component Body
Component Facets
Controlling Access
Using Object-Oriented Development
Best Practices for Conditional Markup
Component Versioning
Components with Minimum API Version Requirements
Validations for Lightning Component Code
Validation When You Save Code Changes
Validation During Development Using the Salesforce CLI
Review and Resolve Validation Errors and Warnings
Lightning Component Validation Rules
Salesforce Lightning CLI (Deprecated)
Using Expressions
Using Labels
Localization
Providing Component Documentation
Working with Base Lightning Components
Working with UI Components
Supporting Accessibility
Using Components
Communicating with Events
Creating Apps
Styling Apps
Developing Secure Code
Using JavaScript
Using Apex
Lightning Data Service
Testing Components with Lightning Testing Service
Debugging
Performance
Reference
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Review and Resolve Validation Errors and Warnings

When you run validations on your Lightning component code, the results include details for each issue found in the files scanned. Review the results and resolve problems in your code.
For example, here is some example output from the force:lightning:lint command.
Results vary in appearance depending on the tool you use to run validations. However, the essential elements are the same for each issue found.

Issues are displayed, one for each warning or error. Each issue includes the line number, severity, and a brief description of the issue. It also includes the rule name, which you can use to look up a more detailed description of the issue. See “Lightning Component Validation Rules” for the rules applied by Lightning code validations, as well as possible resolutions and options for further reading.

Your mission is to review each issue, examine the code in question, and to revise it to eliminate all of the genuine problems.

While no automated tool is perfect, we expect that most errors and warnings generated by Lightning code validations will point to genuine issues in your code, which you should plan to fix as soon as you can.