You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to migrate a production app from v0.7.0 to v1.0.0.
The improvements in 1.0.0 seem very worthwhile and well thought out, and address various other problems - thanks!
The "hashid signing" feature that this gem has implemented (see issue and PR) is causing a totally new set of hashids to be generated.
Would you consider a disable_hashid_signing config option? I appreciate that v 1.0 is not backward-compatible with 0.x but without this option, it seems there is no way to migrate at all?
Another reason to support disabling this feature is that - although useful, and good to enable by default - it's a totally arbitrary solution for the problem, and it prevents compatibility with other hashid tools which would not be encoding using the [HASHID_TOKEN, id] format.
The text was updated successfully, but these errors were encountered:
I am attempting to migrate a production app from
v0.7.0tov1.0.0.The improvements in
1.0.0seem very worthwhile and well thought out, and address various other problems - thanks!The "hashid signing" feature that this gem has implemented (see issue and PR) is causing a totally new set of hashids to be generated.
Would you consider a
disable_hashid_signingconfig option? I appreciate that v 1.0 is not backward-compatible with 0.x but without this option, it seems there is no way to migrate at all?Another reason to support disabling this feature is that - although useful, and good to enable by default - it's a totally arbitrary solution for the problem, and it prevents compatibility with other
hashidtools which would not be encoding using the[HASHID_TOKEN, id]format.The text was updated successfully, but these errors were encountered: