Tom Stuart

What do you mean? Only the clicked <button type="submit"> (or <input type="submit">) element should be included in the form serialization. If all buttons are being included in the serialization, with...

The selector's not the problem. Capybara matches the right button. I put together [this minimal Rails app](https://github.com/tomstuart/capybara-envjs-button-bug) to demonstrate the problem. capybara-envjs copes fine with `` and `` (tomstuart/capybara-envjs-button-bug@9a67d66) but...

Edited title to better reflect the real issue.

I agree that the implementation of `Many` in this gem is not right, but I don’t think the proposed solution is right either. The implementation of `Many` in [the original...

What if we just change the code (on `master`) to be: ``` ruby module Monads class Many # … def self.from_value(value) Many.new(Array(value)) end end end ``` That makes my example...

Okay, great, that’s similar to what I suggested. And your `map(&:values).flatten(1)` is equivalent to just `flat_map(&:values)`, which is what we started with.

The underlying problem is that `Many` is trying to roll two monads into one: ``` ruby >> words = Many.new(['foo', 'bar']) => … >> words.upcase.values => ["FOO", "BAR"] # not...

I can’t edit the issue, but I’ve begun work on “all Range objects are frozen”.

This sounds great! My mental model of the tradeoffs isn’t as clear as it should be, so I could use some help developing my intuition: Am I correct that the...

@nodunayo Hello! Looks like I was too slow on this one. It sounds like it’s all under control now but I’ll keep an eye on the issue in case you...