Document phex-rails register_output_helper :mark_safe option

Author: z1lk

rails/helpers.md

@@ -43,7 +43,11 @@ class Components::Base < Phlex::HTML
   register_value_helper :format_release_date
 
   # Register a Rails helper that returns safe HTML to be pushed to the output buffer.
-  register_output_helper :pagy_nav
+  register_output_helper :paginate
+
+  # If the helper returns HTML as a raw string, `:mark_safe` must be used to brand the output
+  # as safe before it is pushed to the output buffer.
+  register_output_helper :pagy_nav, mark_safe: true
 end
 ```
 

sgml/raw.md

@@ -16,6 +16,6 @@ raw safe(
 
 In Rails, `ActiveSupport::SafeBuffer` objects are also considered safe.
 
-You should avoid using `raw`. If you have to use it, you should avoid using `safe`. Most Rails gems that provide HTML will already mark it as safe if it is safe.
+You should avoid using `raw`. If you have to use it, you should avoid using `safe`. Most Rails gems that provide HTML will already mark it as safe if it is safe. In any case, `phlex-rails` provides a method to register helpers so that using `raw` and `safe` directly is not necessary. See [Registering custom helper adapters](../rails/helpers#registering-custom-helper-adapters).
 
 When you mark a string as `safe`, you are responsible for ensuring there is no unsafe HTML user content in that string. Phlex `raw` method completely bypasses its HTML safety features when given a safe string.