Avoid using `render(...) and return` in example code #45927

r7kamura · 2022-09-01T21:37:59Z

Summary

In the Rails Guides and documentation, there are several examples of using render(...) and return, but this is confusing code for beginners and should be avoided as much as possible in favor of the normal return use.

An action can _contain_ multiple renders/redirects, but only one can be _performed_. Also removes the `and return` recommendation in order to be consistent with the documentation updates from rails#45927

An action can _contain_ multiple renders/redirects, but only one can be _performed_. "Attempting to try to" is redundant. Also removes the `and return` recommendation in order to be consistent with the documentation updates from rails#45927

Avoid using render(...) and return in example code

a5065d4

rails-bot bot added actionpack docs labels Sep 1, 2022

rafaelfranca merged commit ba36ae0 into rails:main Sep 1, 2022

r7kamura deleted the feature/and-return branch September 1, 2022 23:01

artfuldodger mentioned this pull request May 31, 2024

Clarify and make double rendering documentation consistent [ci skip] #51975

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Avoid using `render(...) and return` in example code #45927

Avoid using `render(...) and return` in example code #45927

r7kamura commented Sep 1, 2022 •

edited

Avoid using render(...) and return in example code #45927

Avoid using render(...) and return in example code #45927

Conversation

r7kamura commented Sep 1, 2022 • edited

Summary

Avoid using `render(...) and return` in example code #45927

Avoid using `render(...) and return` in example code #45927

r7kamura commented Sep 1, 2022 •

edited