Vincent Nonnenmacher

Thanks Jeremy ! It could be much helpful to have this mentioned in the documentation as an example as it is a pain to discover that it already as been...

+1 Could you list alternatives, if is seems this project is going to _no-maintainer_ ? sound like : https://github.com/iamisti/mdDataTable is more recently updated.

Hi Yub0 certainly too late, but did you made sure to require the git version of roor in your Gemfile ? I got the same error and finally it worked...

Seems that there no much people working on it. We use it internally so I decided to fork it, for preparing a PR for Rails 6 support but didn't had...

I don't know for Jocelyn use case, but we don't use OOOR in a Rails context, but still the classical Business in Model aproach we don't have too much impendance...

does this means you'll also remove the paragraphe about this PR on [tilt-pipeline gem](https://github.com/jeremyevans/tilt-pipeline#label-Want+it+Upstream-3F) ? We use a lot of such `pipelines` but no problem to use `tilt-pipeline` instead of...

suggestion from @LloydFinch is working and here it is why. Problem is that from JetBrain tools (Rubymine in my case), the launch profile doesn't include the proper '$PATH` you do...

got exactly the same problem when moving a running project from 2.7.x to 3.1. My solution was vastly simple (naive). i.e adding a `kwargs` build from given `*args` Array in...

culprit for me is the line problem for me is on line ``` ruby props = (options[:options][:exclude] || options[:options][:include]) ``` suppose you have something like ``` ruby options = {...

My point is that I have added an orthogonal feature, along with what some people do, with a query parameter (like `&fields="prop1,!excluded,prop2"`), that generate both `:include` and `:exclude` arrays. So...