Previously, when parsing claim values, we used json.UnsupportedTypeError to denote if a claim string value is not of the correct type. However, this could lead to panics if a nil value is present and the Error function of the json.UnsupportedTypeError is called, which does not check for nil types.
Instead, we just now use ErrInvalidType similar to the map claims.
Previously, when parsing claim values, we used
json.UnsupportedTypeErrorto denote if a claim string value is not of the correct type. However, this could lead to panics if a nil value is present and theErrorfunction of thejson.UnsupportedTypeErroris called, which does not check for nil types.Instead, we just now use
ErrInvalidTypesimilar to the map claims.Fixes #315