rails
add :force option to cache!
Before change https://github.com/rails/jbuilder/commit/65dfb3305b1c1ebae550c420a6ab6bd0e21271ec you could pass the :force option to cache! This worked because cache! used Rails.cache.fetch which takes the force option. That commit rewrote cache to use Rails.cache.read and Rails.cache.write which don't do anything with the force option. I use :force extensively in my jbuilder template to send a parameter that will clear and write the cache for the next request. I think this is a worthy feature to have even if it was an undocumented and unintentional feature of jbuilder pre-2.6.0 Closes #424
Thanks for the pull request, and welcome! The Rails team is excited to review your changes, and you should hear from @pixeltrix (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.
@pixeltrix it would be awesome if you could spare a moment to review this. Thank you in advance!
