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

warning: constant ::Fixnum is deprecated #1001

Closed
thinh76 opened this issue Feb 21, 2017 · 11 comments
Closed

warning: constant ::Fixnum is deprecated #1001

thinh76 opened this issue Feb 21, 2017 · 11 comments
Milestone

Comments

@thinh76
Copy link

thinh76 commented Feb 21, 2017

With ruby 2.4.0 release, tests with shoulda matchers are giving the above warnings.

Here is the details referring to deprecating Fixnum
https://bugs.ruby-lang.org/issues/12005

@guialbuk
Copy link
Collaborator

guialbuk commented Jul 5, 2017

Fixed by #1009

@guialbuk guialbuk closed this as completed Jul 5, 2017
@mcmire mcmire added this to the v4.0 milestone Sep 19, 2017
@leomao10
Copy link

leomao10 commented May 1, 2018

Do we have a plan to release v4.0 or backport it to 3.1.x, looks like this issue still existed for the latest shoulda-matcher

@guialbuk
Copy link
Collaborator

guialbuk commented May 1, 2018

Hi @leomao10
You don't need to wait for a new release to have this issue fixed. You can use the master branch.

@chagar
Copy link

chagar commented May 11, 2018

Are there not going to be any more releases? Use master from now on?

@guialbuk
Copy link
Collaborator

guialbuk commented May 11, 2018

Hi @chagar
I suggest you to use the master branch. It's pretty stable. 👍

@mcgoooo
Copy link

mcgoooo commented Jun 19, 2018

hi @guialbuk we are not very comfortable with the solution to use the master branch, is there any way a prerelease gem could be cut? looking at the milestone, there hasn't been any movement on them in a couple of years?

@guialbuk
Copy link
Collaborator

@mcgoooo Not sure what you mean about not having movement in a couple of years. 😕
Anyway, the 4.0 will be released very soon and It will be, besides documentation, exactly the current master branch.
Cheers!

@mcgoooo
Copy link

mcgoooo commented Jun 20, 2018

@guialbuk sorry, i was just looking at the milestone flag from the readme
https://github.com/thoughtbot/shoulda-matchers/milestone/13

Great work on the library btw!

@petergoldstein
Copy link
Contributor

@guialbuk We just ran into this issue, and were wondering if there's an update on either:

  1. 4.0 will be released as a gem
  2. This fix could be backported to the 3.1.x branch and published as a new gem version.

Your last update (~8 months ago) said that 4.0 will be released 'very soon'. Anything I can do to help?

@guialbuk
Copy link
Collaborator

Hi @petergoldstein

  1. 4.0 had significant code changes since the last year, and 4.0.0.rc1 is available: https://github.com/thoughtbot/shoulda-matchers/releases/tag/v4.0.0.rc1
  2. Yes, and the 3.1.3 was released recently with this PR backported: https://github.com/thoughtbot/shoulda-matchers/releases/tag/v3.1.3

But my suggestion is to give a try to the master branch. That's the code with more features and support for edge cases. You should try it, as it runs smoothly in several big projects in production, and by using it people can contribute more towards 4.0.

Cheers

@petergoldstein
Copy link
Contributor

Hi @guialbuk,

Thanks for the quick response.

So I'm using 3.1.3 and still seeing this error:

.../gems/shoulda-matchers-3.1.3/lib/shoulda/matchers/active_model/validate_inclusion_of_matcher.rb:551: warning: constant ::Fixnum is deprecated

Checking the code confirms that this issue exists in 3.1.3 -

Happy to provide a PR for the above issue against the 3.1.3 tag.

Unfortunately using master is not an option for us. Once 4.0.0 is out, we'll be happy to try migrating.

Thanks.

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

No branches or pull requests

7 participants