d055613676
* Adjusting ArticlePolicy for admin only posting The goal of this commit is actually two fold: 1) To add documentation regarding my current emerging understanding of our caching implementation as it relates to our authorization and authentication. 2) Flippiing "on" the feature's core authorization check. Buried within this is the desired normalization of the authorization between the `ArticlePolicy`'s `#create?`, `#preview?`, `#new?`. My testing plan for this is to ask for SRE to spin-up a canary, then test. What does that look like? I'm uncertain because this is nudge closer towards our edge-caching strategy. Which makes robust testing more difficult. Closes forem/forem#16483 Related to #16529, #16571, #16536, #16529 Informs #16490, #16606 * Update spec/requests/editor_spec.rb Co-authored-by: Jamie Gaskins <jgaskins@hey.com> Co-authored-by: Jamie Gaskins <jgaskins@hey.com> |
||
|---|---|---|
| .. | ||
| .keep | ||
| caching_headers.rb | ||
| development_dependency_checks.rb | ||
| edge_cache_safety_check.rb | ||
| image_uploads.rb | ||
| json_api_sort_param.rb | ||
| listings_toolkit.rb | ||
| session_current_user.rb | ||
| valid_request.rb | ||