From bff95987ef1b17077c100e0035db674705e9210e Mon Sep 17 00:00:00 2001 From: Sean Doyle Date: Tue, 3 Oct 2023 14:42:13 -0400 Subject: [PATCH] Resolve Upgrading Rails lint violation Follow-up to [#49474][] Execute documentation change in CI so that the linters can scan the documentation's code blocks. [#49474]: https://github.com/rails/rails/pull/49474#issuecomment-1745519821 --- guides/source/upgrading_ruby_on_rails.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/guides/source/upgrading_ruby_on_rails.md b/guides/source/upgrading_ruby_on_rails.md index 58627182ee8e1..bc2659d238b96 100644 --- a/guides/source/upgrading_ruby_on_rails.md +++ b/guides/source/upgrading_ruby_on_rails.md @@ -266,7 +266,7 @@ responds to various format methods (for example, `rendered.html` and test. For example, the following [assert_match][] assertion will pass: ```ruby -assert_match /some content/i, rendered +assert_match(/some content/i, rendered) ``` However, if your tests rely on `ActionView::TestCase#rendered` returning an @@ -283,7 +283,6 @@ end [assert_match]: https://docs.seattlerb.org/minitest/Minitest/Assertions.html#method-i-assert_match - Upgrading from Rails 6.1 to Rails 7.0 -------------------------------------