rails--rails/actionpack/CHANGELOG.md

## Unreleased

*   Add `redirect_back_or_to(fallback_location, **)` as a more aesthetically pleasing version of `redirect_back fallback_location:, **`.
    The old method name is retained without explicit deprecation.

    *DHH*


Please check [6-1-stable](https://github.com/rails/rails/blob/6-1-stable/actionpack/CHANGELOG.md) for previous changes.
Get rid of the cumbersome fallback_location keyword argument for redirect_back (#40671) 2020-11-24 09:17:11 +00:00			`## Unreleased`

Fix CHANGELOG reference to old method name 2020-11-24 10:00:56 +00:00			* Add `redirect_back_or_to(fallback_location, )` as a more aesthetically pleasing version of `redirect_back fallback_location:, `.
Get rid of the cumbersome fallback_location keyword argument for redirect_back (#40671) 2020-11-24 09:17:11 +00:00			`The old method name is retained without explicit deprecation.`
Make system tests take failed screenshots in `before_teardown` hook Previously we were calling the `take_failed_screenshot` method in an `after_teardown` hook. However, this means that other teardown hooks have to be executed before we take the screenshot. Since there can be dynamic updates to the page after the assertion fails and before we take a screenshot, it seems desirable to minimize that gap as much as possible. Taking the screenshot in a `before_teardown` rather than an `after_teardown` helps with that, and has a side benefit of allowing us to remove the nested `ensure` commented on here: https://github.com/rails/rails/pull/34411#discussion_r232819478 2019-04-21 02:09:50 +00:00
Start Rails 6.2 development :tada: 2020-12-02 23:37:26 +00:00			`DHH`
Make system tests take failed screenshots in `before_teardown` hook Previously we were calling the `take_failed_screenshot` method in an `after_teardown` hook. However, this means that other teardown hooks have to be executed before we take the screenshot. Since there can be dynamic updates to the page after the assertion fails and before we take a screenshot, it seems desirable to minimize that gap as much as possible. Taking the screenshot in a `before_teardown` rather than an `after_teardown` helps with that, and has a side benefit of allowing us to remove the nested `ensure` commented on here: https://github.com/rails/rails/pull/34411#discussion_r232819478 2019-04-21 02:09:50 +00:00
Unify to use 4 spaces indentation in CHANGELOGs [ci skip] Especially, somehow `CHANGELOG.md` in actiontext and activestorage in master branch had used 3 spaces indentation. 2019-06-04 20:47:33 +00:00
Start Rails 6.2 development :tada: 2020-12-02 23:37:26 +00:00			`Please check [6-1-stable](https://github.com/rails/rails/blob/6-1-stable/actionpack/CHANGELOG.md) for previous changes.`