Stafford Brunk

ParseError bug fixed in df8c354e07a6aba084b5b6459d2ac2a8b0be05dc

Probably will.

I'm more of the opinion that `form_group_builder` should handle the option. `form_group` itself should never be aware. ie, why call `form_group` with `form_group: false` and then not get a form...

Hmm, I'm glad there's a solution for this at the moment but that is pretty verbose. I still think I'm partial to a `form_group:false` option.

Well, using `form_group:false` would output the exact same HTML minus the `form_group` wrapper. Using `_without_bootstrap` still requires you to mark up any original fields in the same way that the...

I've got a minimal approach working already if that is of interest. I'm using `webpacker-react` for the client side stuff but the server side is independent. It's pretty heavily influenced...

Ya, I've read through that issue. I actually don't need to turn off inline mode like is specified there. `react-rails` [removes the client require](https://github.com/reactjs/react-rails/blob/f15b255c11cf387ebd3eb583f36ba02df6645b7b/lib/react/server_rendering/webpacker_manifest_container.rb#L19) that inline mode inserts. Simply adding...

Agree to disagree on that one. We use `styled-components` pretty extensively. As they ship all styles via JS and subsequently write a style tag to the DOM on component tree...

Here's a gist of what we are using right now. Like I said, this is a pretty simple implementation. I'm still wondering if a server-only webpack config is a better...

@tomasc I won't be submitting a PR to this repo for server side render support. As we continued to iterate on our solution, it became obvious that a more standalone...