Make sure the render cache is set on create/update.#1025
Open
jsacksick wants to merge 1 commit intoRESTful-Drupal:7.x-2.xfrom
Open
Make sure the render cache is set on create/update.#1025jsacksick wants to merge 1 commit intoRESTful-Drupal:7.x-2.xfrom
jsacksick wants to merge 1 commit intoRESTful-Drupal:7.x-2.xfrom
Conversation
Member
|
It seems that tests are failing due to the Travis build. Can you please run the tests and report if they pass? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I realized the render cache was set only on view() (after doing a doGet on the Resource for instance).
I noticed that when creating/updating an entity (by calling doPost() & doPatch()) on the resource, no cache entry is created.
I spent quiet some time debugging the issue, and realized the check performed in isCacheEnabled() in the Formatter was returning FALSE, because of the $data->getContext().
On view(), CacheDecoratedResource is calling the view method on the CacheDecoratedDataProvider object.
While on create/update, we're not calling the methods on the CacheDecoratedDataProvider.
Additionally, we aren't calling setCacheFragments on the ResourceFieldCollection.
After the patch cache entry is created when I create an entity via the API, On update for some reasons, the cache entry seems to be created from time to time, unsure why...