You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot understand the design of this library at all, it's for quart which is an async library, so why the loaders functions cannot be async? I'm trying to make a database call inside user_claims_loader to get some data based on the identity and encrypt it into the JWT.
It seems like the library is just flast-jwt-extended but with very few extra features and occasionally an async function... The create_access_token function should also be async, since encryption is CPU heavy, could just throw it into a thread and wait for it instead of blocking the event loop. Please explain the reasoning for using so few async functions and not a lot of support for them.
Thank you, have a nice day.
The text was updated successfully, but these errors were encountered:
I cannot understand the design of this library at all, it's for
quart
which is anasync
library, so why the loaders functions cannot beasync
? I'm trying to make a database call insideuser_claims_loader
to get some data based on theidentity
and encrypt it into the JWT.It seems like the library is just
flast-jwt-extended
but with very few extra features and occasionally anasync
function... Thecreate_access_token
function should also beasync
, since encryption is CPU heavy, could just throw it into a thread and wait for it instead of blocking the event loop. Please explain the reasoning for using so fewasync
functions and not a lot of support for them.Thank you, have a nice day.
The text was updated successfully, but these errors were encountered: