-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
replace deprecated constant BLACKLIST_FOR_SERIALIZATION #1473
Conversation
Can you fix the specs? Maybe we need to upgrade devise |
update devise version
@prashant-kiwi you need some help with the tests man? |
@MaicolBen @ThiagoAnunciacao I have fixed the specs. Please have a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we need to have both behaviors and check if the new variable is defined, we cannot leave a lot of people behind for this. Sorry because I said "maybe we need to upgrade to devise" I didn't think is was that big upgrade. Leaving people behind isn't the solution unless we are talking about a very hard change or it's a critical security upgrade
…ley#1473) * replace deprecated constant BLACKLIST_FOR_SERIALIZATION * update devise version * updated devise gem * change devise gem version in all gemfiles * Add condition to check if constant is available in devise Co-authored-by: prashantchauhan627 <prashantchauhan627@gmail.com>
Changed the constant BLACKLIST_FOR_SERIALIZATION with UNSAFE_ATTRIBUTES_FOR_SERIALIZATION.