Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 2.3.6 does not work in Rails 3.2 #115

Open
ryu39 opened this issue Oct 16, 2016 · 2 comments · May be fixed by #116
Open

Version 2.3.6 does not work in Rails 3.2 #115

ryu39 opened this issue Oct 16, 2016 · 2 comments · May be fixed by #116

Comments

@ryu39
Copy link

ryu39 commented Oct 16, 2016

I find that latest version 2.3.6 does not work in Rails 3.2.

In Rails 3.2 environment, bundle exec rake db:seed_fu is failed with 'ArgumentError: wrong number of arguments (given 0, expected 1)...'.
The previous version 2.3.5 works fine.

Here is reproduction script(bash).

gem install rails -v 3.2.22.5

rails _3.2.22.5_ new test_seed_fu
cd test_seed_fu

cat << EOS >> Gemfile
group :development do
  gem 'seed-fu', '2.3.6'
end
EOS

bundle install

script/rails g model User name:string age:integer
bundle exec rake db:migrate

mkdir -p db/fixtures/development
cat << EOS > db/fixtures/development/users.rb
User.seed(:name) do |u|
  u.name = 'User Name'
  u.age = 20
end
EOS

bundle exec rake db:seed_fu
# => rake aborted! ArgumentError: wrong number of arguments (given 0, expected 1) ...

script/rails r "User.seed(:name, name: 'User Name', age: 20)"
# => wrong number of arguments (given 0, expected 1) (ArgumentError) ..
@ryu39 ryu39 linked a pull request Oct 16, 2016 that will close this issue
@ryu39
Copy link
Author

ryu39 commented Oct 16, 2016

I send PR Pull #116 for this issues. Please check it.
Thanks.

@joshuapinter
Copy link
Contributor

@ryu39 Yes, thank you for this. I ran into this after updating my gems and was wondering what was going on because it's just a patch release between my old version of 2.3.4 and the new version of 2.3.6.

I just reverted to 2.3.4 but thanks for reporting the issue and submitting a PR to the owner.

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 a pull request may close this issue.

2 participants