Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multikey status #104

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

fedegiova
Copy link

@fedegiova fedegiova commented May 18, 2022

Hi,
I've added the ability to display multiple keys for the same realname in the status page.

This imply a small API change in the client/status endpoint. In a previous implementation I've tried to preserve the original API
but it then become difficult to handle the response. So I've come up with this version.

The ability to associate multiple keys with one realname is already present on mainline, it was missing only the status page which was displaying only the last one.

Allows the API, cli and web interface to display the status
in case multiple usernames get registered to the same realname.
This introduce an API change int the `client/status` endpoint
which now returns a dict in every cases, otherwise it'll become
difficult for the client handle the data.

Before it the result was:

- no keys: the None string
- one key: a json dict with attributes like {.status } etch
- multiple keys: a json dict with usernames as key and dicts as above
                 as values

Now:

- no keys: empty dict
- multiple / single key: a json dict in the form
                        { "username" : { "status" = "",...}}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant