4e3504fc5b
In theory this should have warned early that the CSRF check will fail, which would have been less puzzling for the developer. However there are several cases where we render forms but the session is inacessible. That's the case of turbo (https://github.com/hotwired/turbo-rails/issues/243) as well as some others. So unless we figure a proper way to detect these cases, we're better to not cause this error. Writing to a disabled session directly will still raise, this only silence it for the specific case of CSRF. |
||
|---|---|---|
| .. | ||
| minitest | ||
| rails | ||
| rails.rb | ||