You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -265,7 +265,7 @@ The options are the same options of ```ActiveSupport::Cache::Store```, plus
265
265
a ```key``` option that will be the prefix of the object cache
266
266
on a pattern ```"#{key}/#{object.id}-#{object.updated_at}"```.
267
267
268
-
The cache support is optimized to use the cached object in multiple request. An object cached on an```show``` request will be reused at the ```index```. If there is a relationship with another cached serializer it will also be created and reused automatically.
268
+
The cache support is optimized to use the cached object in multiple request. An object cached on a```show``` request will be reused at the ```index```. If there is a relationship with another cached serializer it will also be created and reused automatically.
269
269
270
270
**[NOTE] Every object is individually cached.**
271
271
@@ -294,7 +294,7 @@ but in this case it will be automatically expired after 3 hours.
294
294
295
295
### Fragmenting Caching
296
296
297
-
If there is some API endpoint that shouldn't be fully cached, you can still optmise it, using Fragment Cache on the attributes and relationships that you want to cache.
297
+
If there is some API endpoint that shouldn't be fully cached, you can still optimise it, using Fragment Cache on the attributes and relationships that you want to cache.
298
298
299
299
You can define the attribute by using ```only``` or ```except``` option on cache method.
0 commit comments