Skip to content

fix: normalize resolve_client_public_key method#861

Open
lepture wants to merge 1 commit intomainfrom
fix-resolve-key
Open

fix: normalize resolve_client_public_key method#861
lepture wants to merge 1 commit intomainfrom
fix-resolve-key

Conversation

@lepture
Copy link
Member

@lepture lepture commented Feb 14, 2026

If the method is used to resolve a client public key, it is renamed to resolve_client_public_key, and it will only take a client parameter.

@lepture lepture requested a review from azmeuk February 14, 2026 08:13
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
E Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

1 similar comment
@sonarqubecloud
Copy link

Quality Gate Failed Quality Gate failed

Failed conditions
E Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

@azmeuk
Copy link
Member

azmeuk commented Feb 14, 2026

I was wondering in term of design where the best place for resolving client keys would be, this could be in the modules as it is now, or in the client mixin. Since it will probably involve requests maybe the modules is the right place indeed.

@lepture
Copy link
Member Author

lepture commented Feb 14, 2026

Do you mean we should have a client.get_public_key() method?

@azmeuk
Copy link
Member

azmeuk commented Feb 14, 2026

Well, this is an option. What do you think?

@lepture
Copy link
Member Author

lepture commented Feb 16, 2026

@azmeuk I think we can add the client method later. Maybe in next release.

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.

2 participants