Validate uniqueness always failing after one fail about judge HOT 8 CLOSED

I need to dig into this, but I think it's a problem that only happens in development due to Rails' autoloading classes. cf. #16

from judge.

I will try in production, thank you.

from judge.

Thanks @joecorcoran, in production it is working very well.

I am using the master version

gem 'judge', git: 'git://github.com/joecorcoran/judge.git'

What version would you recommend to use?

from judge.

Use the latest version on Rubygems unless you are relying on a bug fix on master, in which case stick with the git option. I should release a new version soon.

from judge.

@ricardodovalle Did you solve this issue? I mean in development, not in production.

@joecorcoran the new version that you were mentioning in the last post (may 15), was released? and if it was released, it solve the problem in development mode too?

Thanks.

from judge.

Not sure about production env, but it sure is still broken in develpment mode, I have seen other issue for this closed. I am using 'master' commit e79cda4.

I think this is a 'Singleton' usage problem, look here:

    def expose(klass, *attributes)
      attrs = (@@exposed[klass] ||= [])
      attrs.concat(attributes).uniq!
    end

This is a workaround that works for me (in development):

before, fragile:

Judge.configure do
  expose User, :username
end

after, solid:

Judge.config.exposed[User] = [:username]

from judge.

Same error here. Tried to change it as @rubyconvict suggested, but the error still occurs in development and production mode.

Edit: actually there was a typo in my params list. Seems to be ok now with @rubyconvict suggestion, but the duplicated field error message doesn't appear anymore.

from judge.

Glad I could help.

from judge.