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
The verified claims spec is difficult to implement in typed languages.
The verified claims requested from a user. Array of claim types or Claims Specs for self signed claims eg: ["name", {type: "email", essential: true, iss: [{did: 'did:web:uport.claims'}]}]
Having an array of either String or Object is fine in JS but is a nightmare to serialize/deserialize in typed languages.
Not only that, but the logic needed to parse the request gets more complicated and is not necessarily backwards compatible.
Since this is not widespread it may be worth using a different field for the verified claim query in the request instead of complicating the logic of existing fields and breaking current implementations.
The text was updated successfully, but these errors were encountered:
The verified claims spec is difficult to implement in typed languages.
Having an array of either
String
orObject
is fine in JS but is a nightmare to serialize/deserialize in typed languages.Not only that, but the logic needed to parse the request gets more complicated and is not necessarily backwards compatible.
Since this is not widespread it may be worth using a different field for the verified claim query in the request instead of complicating the logic of existing fields and breaking current implementations.
The text was updated successfully, but these errors were encountered: