* Add article's record key to Fastly Surrogate-Key to separate caches After #4744 we successfully setup an auto purging system based on Fastly's surrogate key based cache and purging API. Unfortunately this worked only in the `:show` action as comments are their own tree-based resource. The `:index` though, is related to a single article, so without the article's record key in the `Surrogate-Key` header the first time we hit the API the result would become the value stored in Fastly's API, for all articles. * Fix commentable mock for job spec * Add comment.commentable.purge to the worker as well * Add more thorough tests for commentable |
||
|---|---|---|
| .. | ||
| bust_cache_worker_spec.rb | ||
| calculate_score_worker_spec.rb | ||
| create_first_reaction_worker_spec.rb | ||
| send_email_notification_worker_spec.rb | ||