Alexander Korolev
Alexander Korolev
It would be nice to add at least some details next time...
I think I know this behaviour, I also have not investigated deep. It seems like metadata from provider has lifetime. Most simple solution would be just refresh client once per...
Yes, it is in client. We do not fetch metadata each time, developers are free to write particular logic to handle this. I recently had a case, there I need...
@andrewbaxter I do not know, it would be idiomatic only for google. Current example in top level readme is already quite complex. We probably should keep it simple. But more...
~~If it could be implemented with feature guard, I am not against it~~. Oops, I understood, that this will allow to change behavior, which we should not allow. It would...
I would like to check information on topic https://auth0.com/docs/secure/tokens
I have not touched it as I wanted to keep API same as before, until OpenAPI will show it is stable. Actually seems like now nothing prevents us. Only precondition...
As I understood from other sources and I think it also good idea - better to use builder pattern. And this can be extended to whole API idea.
Hi @rblaine95! It is interesting idea, thank you! I am currently trying to avoid `Debug` in structures with sensitive data, but this maybe a better option. If we have such...
`update.ts` is only automation tool for releases, the work horse there is `examples/openapi.rs`. It has already some additional configuration for field types. Maybe potentionally extended to keep list of sensitive...