Contents
Why is LWC cacheable true?
In this approach, it improves the component’s performance as it can display the cached data fast from client side storage rather an extensive trip to server. To improve runtime performance, annotate the apex method with [@AuraEnabled (Cacheable=true)] to caches the method results on the client.
What is @AuraEnabled cacheable true?
To set cacheable=true , a method must only get data. It can’t mutate data. Marking a method as storable (cacheable) improves your component’s performance by quickly showing cached data from client-side storage without waiting for a server trip.
What is the use of AuraEnabled annotation?
The @AuraEnabled annotation enables client- and server-side access to an Apex controller method. Providing this annotation makes your methods available to your Lightning components (both Lightning web components and Aura components). Only methods with this annotation are exposed.
How can you improve runtime performance of APEX calls by caching results on the client?
To improve runtime performance, annotate the Apex method with @AuraEnabled(cacheable=true) , which caches the method results on the client. To set cacheable=true , a method must only get data, it can’t mutate (change) data.
What is a enqueueAction action in lightning?
enqueueAction(action) adds the server-side controller action to the queue of actions to be executed. Rather than sending a separate request for each individual action, the framework processes the event chain and batches the actions in the queue into one request. The actions are asynchronous and have callbacks.
Can you use cacheable = true in DML?
Yes, future methods are a separate transaction, and are not subject to the limits of cacheable=true methods. Note that you should avoid DML in such a method, because there is no guarantee the method will be called every time (e.g. if a response is already in the cache).
When to use cacheable = true in Lightning?
FYI, as of October 2020, @AuraEnabled (Cacheable = true) methods CAN publish platform events, which can be used to fire a subsequent trigger to execute DML code. Note that the events must be defined as “Publish Immediate”, and not “Publish after commit”.
Do you cache the result individually or combined?
LWC: Does @AuraEnabled (cacheable=true) cache the result individually or combined? Prequel: I have several methods in need of the same @wire operations. The approach I initially took was to make a new utilities component just for the wire operations and then use the pubsub library to fire the data that was retrieved.
How does marking a method as cacheable improve performance?
Marking a method as cacheable improves your component’s performance by quickly showing cached data from client-side storage without waiting for a server trip. But it’s not clear to me whether the cache is for all components or is it individual per component.