Should Rails/Output Skip migrations and generators by default?

[schwern]

The Rails/Output cop is flagging p and puts inside migrations and generators saying I should use the logger instead. Rails.logger does not appear to be a drop in replacement for them in these contexts. Rails.logger.info goes to log/dev.log which is incorrect, it should be displayed to the screen like the rest of the generator or migration output.

Should Rails/Output be disabled by default for generators and migrations? Or does Rails/Output need extra documentation about the right thing to do inside generators and migrations?

[andyw8]

For migrations, you can use say and say_with_time:
https://guides.rubyonrails.org/active_record_migrations.html#changing-the-output-of-running-migrations

For generators, the readme method can output the contents of a file:

https://guides.rubyonrails.org/generators.html#readme

Does that cover your use cases?

[koic]

If this issue is the same problem as #934 will be solved by #965.