Repository navigation
feat: add token status and prepare 3.1.0 - #7
Merged
Merged
Conversation
StefaniOSApps
force-pushed
the
feat/token-status
branch
2 times, most recently
from
October 8, 2026 22:12
a3e39de to
b6aff12
Compare
Expose GET /v1/token/status as client.token.status(). It returns the token's display name, granted scopes and expiry, needs no scope and changes no data. Known scopes are TokenScope members; a scope added by a newer API stays a plain string instead of failing the response. Add shared contract cases for the new operation, including an unknown scope and the wrong-status case, and compare expiresAt as an instant.
StefaniOSApps
force-pushed
the
feat/token-status
branch
from
October 8, 2026 22:56
b6aff12 to
ccefdba
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add
client.token.status()for the newGET /v1/token/statusendpoint and prepare Python client 3.1.0. It returns the token's display name, scopes and expiry, needs no scope and changes no data.Known scopes are
TokenScopemembers. A scope added by a newer backend stays a plain string instead of failing the response. The shared contract fixtures gain thetoken.statusoperation.