Francisco

Bundler was working OK before installing jruby, and despite the `type` command showing that the right binary was called, I also tried calling it directly with the full path.

This is my output: ``` $ chruby 2.1.6 2.2.1 * 2.2.2 jruby-9.0.0.0.pre2 $ bundle -v Bundler version 1.9.9 $ head $(which bundler) #!/opt/rubies/2.2.2/bin/ruby # # This file was generated by...

After deleting jruby I realized I could fix the warning by also removing the gem. ``` gem uninstall jruby-launcher-1.1.1-java ``` So I am no longer sure this is a real...

I am not sure if this was the case before, but this is the current status: ``` ruby-build 2.2.0 /opt/rubies/2.2.0 ruby-build jruby-9.0.0.0 /opt/rubies/jruby-9000 chruby 2.2.0 ``` Warnings everywhere about jruby-launcher...

IMHO it should be possible to disable warnings for third party code. Right now I depend on a library to test each of my React components and my test reports...

I think the right solution should be the one mentioned by @glebec Currently the whole test suite shutdowns thinking that throwing an error within a hook is a "setup -infrastructure"...

Great! I absolutely like your functional approach. Validations is a great use case for FP. It is also clear that one could build a layer on top to build objects...

If it helps, this is my line of thought: ```javascript const normalizeString = (rules, {default}) => (value, f) => { let before = value || 'anonymous' let result = f(before)...

I must retract myself in one of the points. Now I believe coercions must be done before validation. Any modification after validation seems to me now awfully conflicting (like setting...

> > Try to run the latest version of the app using the same command with the `--debug` flag. You will see which note was processed last before the app...