We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, thank you for the project and work!
I mean, for example, when obtaining the token pairs, we perform the mutation like this:
mutation TokenAuth($username: String!, $password: String!) { tokenAuth(username: $username, password: $password) { token refreshToken payload refreshExpiresIn } }
Suppose I want to rename the field token to access and refreshToken to refresh and perform the mutation like this:
token
access
refreshToken
refresh
mutation TokenAuth($username: String!, $password: String!) { tokenAuth(username: $username, password: $password) { access refresh payload refreshExpiresIn } }
I saw that the name definitions are done here:
django-graphql-jwt/graphql_jwt/mixins.py
Line 21 in 704f24e
Line 24 in 704f24e
Is it possible to make these fields configurable via settings definition or is it a breaking change?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi, thank you for the project and work!
I mean, for example, when obtaining the token pairs, we perform the mutation like this:
Suppose I want to rename the field
token
toaccess
andrefreshToken
torefresh
and perform the mutation like this:I saw that the name definitions are done here:
django-graphql-jwt/graphql_jwt/mixins.py
Line 21 in 704f24e
and here:
django-graphql-jwt/graphql_jwt/mixins.py
Line 24 in 704f24e
Is it possible to make these fields configurable via settings definition or is it a breaking change?
The text was updated successfully, but these errors were encountered: