Advanced Lightning Components
1 like1,329 views
This document discusses advanced topics related to Lightning Components. It begins with an agenda that covers best practices, debugging, demos, and Q&A. In the best practices section, it recommends using $A instead of "aura" when accessing APIs, avoiding method name collisions, and using the official API. It also suggests handling events efficiently and avoiding unnecessary DOM manipulation. The debugging section provides tips for using browser developer tools and enabling pause on caught exceptions. Demos and Q&A were also on the agenda.
Advanced Lightning Components
- 1. Advanced Lightning Components Skip Sauls Director of Product Management ssauls@salesforce.com @SkipSauls Kris Gray PMTS, Aura Framework kgray@salesforce.com @grayjustise John Buchanan PMTS, Aura Framework jbuchanan@salesforce.com
- 2. Safe harbor statement under the Private Securities Litigation Reform Act of 1995: This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be deemed forward- looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services. The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of any litigation, risks associated with completed and any possible mergers and acquisitions, the immature market in which we operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of salesforce.com, inc. is included in our annual report on Form 10-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of our Web site. Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-looking statements. Safe Harbor
- 4. Use createComponent • newComponentAsync and other variants are being deprecated Use $A when accessing APIs • “aura” is being deprecated Avoid method name collisions • Use unique method names for server vs. client-side methods Use the official API • Don’t use undocumented members on $A or components Efficient events • Don’t handle your own events Don’t use setTimeout Best Practices Advanced Lightning Components
- 5. Component Lifecycle • Ensure that you really need to use a renderer DOM Manipulation • “If you didn’t create it, don’t touch it.” – Doug Chasman CSS • Always use properly namespaced rules – See above about not touching things you don’t own 3rd Party Libraries • Ensure that you really need to load jQuery, Bootstrap, etc. before doing so • Remember that these aren’t single-page applications (SPAs), especially in mobile clients Use Actions • Actions are optimized by the framework, unlike XHRs Best Practices Advanced Lightning Components
- 6. • Many apps such as Salesforce1 and Lightning Experience catch most exceptions to provide a better user experience. • Enable features such as “Pause On Caught Exceptions” in the browser debugger to ensure that you don’t miss something. Debugging – Client Side Advanced Lightning Components Google Chrome Developer Tools Apple Safari Web Inspector Mozilla Firefox Firebug Mozilla Firefox Developer Tools Microsoft Edge Developer Tools Microsoft IE11 Developer Tools
- 7. Use the debugger statement Enable Pause on Caught Exceptions Turn on Debug for Lightning Components Leverage the browser Developer Tools features Debug on more than one client Debugging – Client Side Advanced Lightning Components
- 8. Demos
- 9. Q&A
- 10. Thank you