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 chatted with @matheus23 earlier today about the updated powerline syntax & changes from past iterations. [Philipp, feel free to correct me if I'm wrong on any of the below but wanted to capture here.]
TL;DR he's in favour, but raised that it's too easy to omit the sub field accidentally. Two suggestions:
Require that you use an explicit sub: null if omitted
Use a glob sub: "did:*
The glob has the disadvantage that it looks like you can restrict DIDs by scheme (did:dns:*), when I'm pretty sure that's not the behaviour that we want.
I am in favour of making the Null explicit. In most libraries you're already going to have to give have some variation on audience: Option<DID>, so let's just render None to null as a default.
Any objections?
The text was updated successfully, but these errors were encountered:
expede
changed the title
Powerline optional subject synatx
Explicit null to omit subject (powerline)
Feb 27, 2024
I chatted with @matheus23 earlier today about the updated powerline syntax & changes from past iterations. [Philipp, feel free to correct me if I'm wrong on any of the below but wanted to capture here.]
TL;DR he's in favour, but raised that it's too easy to omit the
sub
field accidentally. Two suggestions:sub: null
if omittedsub: "did:*
The glob has the disadvantage that it looks like you can restrict DIDs by scheme (
did:dns:*
), when I'm pretty sure that's not the behaviour that we want.I am in favour of making the
Null
explicit. In most libraries you're already going to have to give have some variation onaudience: Option<DID>
, so let's just renderNone
tonull
as a default.Any objections?
The text was updated successfully, but these errors were encountered: