Instead of serialising and deserialising stored claim values multiple times, use json.RawMessage to allow serialisation to be delayed (when parsing) and done up-front (when creating a new token). This is necessary because the exact encoding used will depend on the original type, and this information is lost when decoding and then re-encoding absent that type information.
Fixes: #47
Instead of serialising and deserialising stored claim values multiple times, use json.RawMessage to allow serialisation to be delayed (when parsing) and done up-front (when creating a new token). This is necessary because the exact encoding used will depend on the original type, and this information is lost when decoding and then re-encoding absent that type information.