-
Notifications
You must be signed in to change notification settings - Fork 165
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
whats the status on this gem? #46
Comments
Seems pretty much dead, have you found any alternatives? |
@jafuentest this one seems to be fresher: https://github.com/amw/mongoid_enum |
@FunkyloverOne @jafuentest - unfortunately that one also looks to be dead. :( |
It looks like the more recent pull-requests that came in for this gem all broke the build. I wouldn't blame @thetron for ignoring those. As an attempt at rejuvenating this project, I just submitted 4 new pull-requests that all together bring things back up to snuff while also adding Mongoid 6 support. Oh, and they run green too. 💚
@thetron If you have the time to review these pull-requests and publish a new release of mongoid-enum to rubygems, that would be super awesome! Hopefully, these pull-requests make your life a bit easier. Thanks! |
Looks like Mongoid 7 was released last month, I hope this gem can be updated, enums are really very useful! |
Guys, you can switch to enumerize, it works well with Mongoid 6.4 for me, guess it will also work for Mongoid 7. |
Since this gem does not get updated by three years I wrote a new gem called |
Hi, @rmm5t Why do not we make a fork do we maintain this or do we create our own gem? I have had many problems and I would like to help solve them. 👍 |
@kenneth1870 I'm not a huge fan of forking open source projects for reasons such as this unless all other options are exhausted, but I understand your frustration. However, in the meantime, I just created a gem "mongoid-enum", github: "rmm5t/mongoid-enum", branch: "working" @thetron If you need help maintaining this project, I'm willing to help get this repository up to snuff and help publish a new gem to rubygems. Feel free to review my github and rubygem history. |
Thanks @rmm5t that works for me |
@rmm5t it looks great, but could you update the branch to support mongoid 7.0.2, please? |
I've just found this project: https://github.com/lwe/simple_enum |
BTW I can confirm that I use https://github.com/brainspec/enumerize with Mongoid 7 in production |
@daniloakamine I haven't touched the project that relied on this particular pull-request in a while now, but I'll probably be near that codebase in the next couple weeks or so. If I find the time, I'll add another PR to allow mongoid 7, but no promises. Considering these PRs aren’t being reviewed or merged, it might be better to consider alternative gems as necessary. |
@rmm5t well, let it go. |
I'm working on migrating an app from this gem to enumerize (which seems to be the most widely used and supported enum library that supports MongoID), and the transition is tedious, but fairly simple if you know the sticking points, so I thought I'd share in case anybody else needs to do this:
The differences to remember are:
There are other added conveniences that may allow you to clean up your code - for instance, enumerize integrates with rails_admin automatically, so you can remove custom enum code for rails_admin, but for the most part everything else works the same. |
Also please keep in mind this issue guys: brainspec/enumerize#333 |
Hey guys, I have a question related to enumerize gem, We upgraded all app stacks and we are using mongoid 7, and we had to change from mongoid-enum to enumerize, and we have a problem related to multiple enumerize. The problem is no matter how I use the field + enjumerize syntax I do not have the old values which are in the DB, even after I do a mongorestore the values are not saved in field. Is there something that I missed when I changed the model field attributes from enum to enumerize? |
@valentinbotog You'll have better chances of getting a reply on the enumerize page. I found it much simpler to migrate to mongoid_enumerable. |
@jafuentest - thanks, I added the same comment on enumerize github page yesterday, still waiting for an example of how to use multiple and have the values from mongorestore. |
Just looking through and noticing that there has not been a commit in 2 years, and PRs that seem to have been ignored for some time as well. Does this gem need new maintainers? Is there an alternative people have switched to?
The text was updated successfully, but these errors were encountered: