diff options
author | David Yip <yipdw@member.fsf.org> | 2017-12-06 16:19:43 -0600 |
---|---|---|
committer | David Yip <yipdw@member.fsf.org> | 2017-12-06 16:19:43 -0600 |
commit | 017fc81caf8f265e5c5543186877437485625795 (patch) | |
tree | cd2b7f699b1f067f284826e588a257771d285fb0 /app/javascript/flavours/glitch/util/base_polyfills.js | |
parent | 5bed0f10ed4628049ca14fb188804654574be1bf (diff) |
Prepend check_enabled_deletion to Settings::DeletesController (#229)
The specs for Settings::DeletesController include an example that sets Settings.open_deletion to false and expects the "if deletion is not available, redirect to root" logic to run. However, this spec does not set up a user, which means that the spec (intentionally or otherwise) expects this redirection to work with unauthenticated access. We should preserve that behavior. To do so, we prepend the deletion check to the action chain set up by Settings::BaseController, so that said check occurs before the authenticate_user! check.
Diffstat (limited to 'app/javascript/flavours/glitch/util/base_polyfills.js')
0 files changed, 0 insertions, 0 deletions