Address ruby 3.0 support

[kimyu92]

Since Rails 7 requires minimum ruby 2.7+

This PR is intended to separation of positional and keyword arguments introduced since ruby 2.7 and it's necessary for ruby 3.0

[kimyu92]

@armiiller Possible to look at this change?

[armiiller]

Looks good! Thanks @kimyu92

[tnir]

The upstream now includes this change on its default branch (master) (see attr-encrypted#383).

[kimyu92]

@tnir Unfortunately, it's still missing rails support from upstream.

3637c91
515cf71
eafd77a

[tnir]

@kimyu92 Excellent! Did you try to create PR in the upstream? Happy if you do so 🙏

[tnir]

cc @armiiller (the original author of these commits)

[armiiller]

Hi @tnir - Are you asking that I make a PR to attr-encrypted/attr_encrypted ?

It's been a while since I touched this repo, it was primarily mean as a blog post / temporary gem while users moved from attr_encrypted to native rails encryption. There were no plans to maintain this gem as a "replacement". Native rails encryption should be the solution

[kimyu92]

@tnir I'm happy to port the commits to original repo

@armiiller you're right about the native rails encryption should be the way to go, however, in real world scenario, it might not be possible to transition to native solution immediately based on the size of app and priority.

[armiiller]

FYI - I think I didn't try to PR these into the main branch because it would be a major breaking change for the attr_encrypted library. You would need some sort of "opt in" configuration so you don't break everything in existing repos that were already using attr_encrypted. The method prefix broke a lot of items, and thus why it was a fork

Something to consider if making a PR. Maybe something for an initializer file or something

[tnir]

Thanks @armiiller. Yes, I asked you so. I agree with @armiiller. I will recheck how the migration in the real world works in a week.