-
Notifications
You must be signed in to change notification settings - Fork 521
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
[BUG] Handle get key operation when no tag has been set #3256
[BUG] Handle get key operation when no tag has been set #3256
Conversation
Signed-off-by: Patrick St-Louis <[email protected]>
Signed-off-by: Patrick St-Louis <[email protected]>
Signed-off-by: PatStLouis <[email protected]>
another fix could be to change this line: from: if kid:
tags = {"kid": kid}
else:
tags = None to if kid:
tags = {"kid": kid}
else:
tags = {} I believe this would be more consistent as a fix since all keys will have a tags object. Any opinion? |
Signed-off-by: PatStLouis <[email protected]>
Signed-off-by: PatStLouis <[email protected]>
I made a combination of @jamshale suggestion and the latter idea. |
Signed-off-by: PatStLouis <[email protected]>
|
…oundation#3256) * Bug-fix Signed-off-by: Patrick St-Louis <[email protected]> * Update in_memory.py Signed-off-by: Patrick St-Louis <[email protected]> * linting Signed-off-by: PatStLouis <[email protected]> * apply better suggestion Signed-off-by: PatStLouis <[email protected]> * set empty tags object instead of none for consistency Signed-off-by: PatStLouis <[email protected]> * remove unnecessary change in the in memory wallet Signed-off-by: PatStLouis <[email protected]> --------- Signed-off-by: Patrick St-Louis <[email protected]> Signed-off-by: PatStLouis <[email protected]>
Handle cases where a key doesn't have a tags property.
@dbluhm @jamshale small but critical bug introduced by my last PR, I was under the impression every key had tags by default but it doesn't seem like so, this will handle such cases.