Skip to content

Conversation

@laserlemon
Copy link
Contributor

This is useful in using Bootstrap Forms with third party libraries such as Ransack, whose queries and values do not always conform fully to the Active Model API.

A class's name, while model_name is preferred, is still a good fallback.

This is useful in using Bootstrap Forms with third party libraries such
as Ransack, whose queries and values do not always conform fully to the
Active Model API.

A class's name, while model_name is preferred, is still a good fallback.
@mattbrictson
Copy link
Contributor

Looks good to me! Thanks for the PR and the test. 🙌

Can you add a CHANGELOG entry so that I can merge this?

@laserlemon
Copy link
Contributor Author

@mattbrictson Thank you! I just pushed an update to the changelog.

@mattbrictson
Copy link
Contributor

Thanks for your contribution! 🙇

@mattbrictson mattbrictson merged commit ed591c1 into bootstrap-ruby:master Oct 1, 2016
@laserlemon laserlemon deleted the form-objects-without-model-names branch October 2, 2016 22:41
@laserlemon
Copy link
Contributor Author

Great, thank you! Do you have a scheduled time for the next release so I can check back in?

@mattbrictson
Copy link
Contributor

For non-critical bug fixes, I usually push a release every 6 weeks. So the next release would be early November. In the meantime you can update your Gemfile to use the master branch:

gem "bootstrap_form", :github => "bootstrap-ruby/rails-bootstrap-forms"

@mattbrictson
Copy link
Contributor

FYI, I just released 2.5.2 with this included. 🚢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants