Fixes #352 - This adds a hidden feature that allows the storage of vec to skip base64 for some users.
We can't apply this into base64urlsafedata because features taint and having a flag to skip base64 would break wasm and json front ends. So as a result, the only way to proceed is to swap the type in the struct based on the cfg flag. It is a teeny bit messy because it introduces some useless into()/from() where without the feature we are doing base64 into base64, but it's needed when the feature is enabled.
I can't think of a better way to actually achieve this though without breaking existing users horrendously. @micolous do you have any better ideas perhaps?
[ x ] cargo test has been run and passes
[ ] documentation has been updated with relevant examples (if relevant)
Fixes #352 - This adds a hidden feature that allows the storage of vec to skip base64 for some users.
We can't apply this into base64urlsafedata because features taint and having a flag to skip base64 would break wasm and json front ends. So as a result, the only way to proceed is to swap the type in the struct based on the cfg flag. It is a teeny bit messy because it introduces some useless into()/from() where without the feature we are doing base64 into base64, but it's needed when the feature is enabled.
I can't think of a better way to actually achieve this though without breaking existing users horrendously. @micolous do you have any better ideas perhaps?