Conversation
|
There are still quite a few projects on Rails 4, I would suggest not breaking compatibility with them. |
|
I would suggest a 1.7 version with old simple_enum api, rails 5 and mongoid 6 compatibility. In my case I have a big project working with simple enum old api and I'm trying to upgrade to rails 5. |
|
Hey @ritxi, sorry for the late response, how can I help you with the Rails 5 related migrate and mongoid 6? |
|
TBH, according to semver it's very tricky to actually be able to provide a 1.x release that is breaking backwards compatibility. |
|
Hi @lwe, I just published this pull request if it would be helpful for somebody, I'm using it in production with success. I suggested you to do 1.7 release just to let people in the same situation as me to be able to upgrade newer rails/mongo versions without the need to upgrade to the new api. |
|
Are the changes backwards compatible towards Rails 4 and Mongodb 5? |
|
Hey @ritxi, I've seen that you did a recent change here. Anything I can do and anything required, that this can be applied to |
|
Hi, |
Keep same api but make it compatible with rails 5.x and mongoid 6.x