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

Use Protocol V3 on python binding #3623

Closed

Conversation

FirelightFlagboy
Copy link
Contributor

@FirelightFlagboy FirelightFlagboy commented Nov 25, 2022

  • Correct definition of RealmUpdateRoles for the introduced reply user_revoked in 3.1.

TODOS

  • How the backend can handle v2 & v3 ?
  • Does the client need to handle v2 & v3 ?

@FirelightFlagboy FirelightFlagboy force-pushed the 3618-correct-definition-of-protocol-scheme branch 3 times, most recently from d8e9240 to 0ec32ae Compare November 28, 2022 08:16
@FirelightFlagboy FirelightFlagboy marked this pull request as draft November 28, 2022 08:16
@FirelightFlagboy FirelightFlagboy force-pushed the 3618-correct-definition-of-protocol-scheme branch 2 times, most recently from e917cda to 5807329 Compare December 6, 2022 15:41
- Correct definition of `RealmUpdateRoles` for the introduced reply `user_revoked` in `3.1`.
@FirelightFlagboy FirelightFlagboy force-pushed the 3618-correct-definition-of-protocol-scheme branch from 5807329 to dcc72fe Compare December 7, 2022 10:00
@touilleMan
Copy link
Member

replaced by #4515, python bindings have access to all API versions

@touilleMan touilleMan closed this Jun 9, 2023
@FirelightFlagboy FirelightFlagboy deleted the 3618-correct-definition-of-protocol-scheme branch March 6, 2024 10:39
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.

Use protocol v3 in python binding Correct definition of protocol scheme
2 participants