Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Add GitHub handle to pallet-identity #13728

Closed
ggwpez opened this issue Mar 27, 2023 · 6 comments
Closed

Add GitHub handle to pallet-identity #13728

ggwpez opened this issue Mar 27, 2023 · 6 comments
Labels
J0-enhancement An additional feature request. Z1-easy Can be fixed primarily by duplicating and adapting code by an intermediate coder

Comments

@ggwpez
Copy link
Member

ggwpez commented Mar 27, 2023

(I cant find an issue in case this was already proposed)

Would be nice to have GitHub handles in the identity data. Especially with the Polkadot fellowship being so reliant on it.
They are automatically verifiable by registrates via edited profile text, so no problem.

@ggwpez ggwpez added J0-enhancement An additional feature request. Z1-easy Can be fixed primarily by duplicating and adapting code by an intermediate coder labels Mar 27, 2023
@bkchr
Copy link
Member

bkchr commented Mar 27, 2023

We can just add the github handle the to the additional fields?

pub additional: BoundedVec<(Data, Data), FieldLimit>,

@ggwpez
Copy link
Member Author

ggwpez commented Mar 27, 2023

We can just add the github handle the to the additional fields?

Yes but registrats cannot verify that since it is "custom" data, so the interpretation of it is not defined.

@ggwpez
Copy link
Member Author

ggwpez commented Mar 27, 2023

For example one person writes "Github handle", the next "github" and so on. Its probably easier to extend the enum since we have Twitter and Riot it is already opinionated.

@bkchr
Copy link
Member

bkchr commented Mar 27, 2023

For example one person writes "Github handle", the next "github" and so on.

Yes, but then you need to specify what kind of key is the correct one.

Its probably easier to extend the enum since we have Twitter and Riot it is already opinionated.

I would argue that this should not have been done and it should have been generic from the beginning.

@ggwpez
Copy link
Member Author

ggwpez commented Mar 27, 2023

I would argue that this should not have been done and it should have been generic from the beginning.

Yea probably better to start with this. Then we can inject the "custom" type via the config trait.

@bkchr
Copy link
Member

bkchr commented Apr 26, 2023

Closing in favor of: paritytech/polkadot-sdk#179

@bkchr bkchr closed this as completed Apr 26, 2023
@github-project-automation github-project-automation bot moved this from Backlog to Done in Runtime / FRAME Apr 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
J0-enhancement An additional feature request. Z1-easy Can be fixed primarily by duplicating and adapting code by an intermediate coder
Projects
Status: Done
Development

No branches or pull requests

2 participants