Readme

[ghost]

Included:

• Sample controller (where to use it)
• Explanation of the form duck type
• Installation instructions
• TravisCI badge
• Rubygems badge

Missing: Logo

Notes:

• Noticed that this assumes the person using the gem is using Minitest. not sure if there should be an option to create a Minitest test file or not if something else is being used?
• Not sure how deep to go in terms of sample controller code, so I just added a big chunk and removed the Pundit-related code.

[jackjennings]

I'm not sure that I can really confidently say that the behavior of passing method calls through to the record isn't a kind of duck-type, but I just think that it's more accurate to say that the methods that I mentioned and their arguments are closer to how that concept would be applied traditionally.

The idea too is that the interface for the form objects is very small: an initializer and a method call. Everything else can be loose, as long as those qualities exist. Since they are required to use the submit controller method, it's worth providing an code example at the top of Usage.

[jackjennings]

Regarding test code: If someone wants to include RSpec code we can update the generator, though since we're not using RSpec at this point I'd be fine holding off.

[jackjennings]

Logo is fine to ignore ;)