You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove the global output buffer; compile on render_in (#1432)
* Remove the global output buffer; compile on render_in
* Use rails main
* Fix linting issues
* Fix bad merge
Co-authored-by: Joel Hawksley <[email protected]>
Copy file name to clipboardExpand all lines: docs/known_issues.md
-22Lines changed: 0 additions & 22 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,28 +9,6 @@ title: Known issues
9
9
10
10
ViewComponent [isn't compatible](https://github.com/github/view_component/issues/241) with `form_for` helpers by default.
11
11
12
-
### Using a Global Output Buffer
13
-
14
-
Since 2.52.0
15
-
{: .label }
16
-
17
-
Experimental
18
-
{: .label .label-yellow }
19
-
20
-
One possible solution to the form helpers problem is to use a single, global output buffer. For details, please refer to [this pull request](https://github.com/github/view_component/pull/1307).
21
-
22
-
The global output buffer behavior is opt-in. Prepend the `ViewComponent::GlobalOutputBuffer` module into individual component classes to use it.
23
-
24
-
For example:
25
-
26
-
```ruby
27
-
classMyComponent < ViewComponent::Base
28
-
prependViewComponent::GlobalOutputBuffer
29
-
end
30
-
```
31
-
32
-
It is also possible to enable the global output buffer globally by setting the `config.view_component.use_global_output_buffer` setting to `true` in your Rails config.
33
-
34
12
## Inconsistent controller rendering behavior between Rails versions
35
13
36
14
In versions of Rails < 6.1, rendering a ViewComponent from a controller doesn't include the layout.
0 commit comments