Charlie Jonas

I may be mistaken, but the issue isn't that ANY other app can access a password created with this... but instead that ANY node process can? At least on OSX,...

would love to see this as well

> As a workaround you could just clone an object and then get JSON patch to see the changes, but it's definitely a higher performance cost that tracking in the...

even just being able to drop all the functions in a subfolder 1 level deep would make a big difference. That way at least you have single folder containing ONLY...

I also have a use case where I want to generate the types without the client. We are using `RTKquery` code generation on our front end (which uses this library)...

This seems to work ok... ```typescript const isRestObject = (obj: any) => { let proto = obj.__proto__; while (proto) { if (proto === RestObject.prototype) { return true; } proto =...

Unfortunately it's not yet been implemented.. My use case has always been on-org (using the session_id). Refresh token functionality would not be too hard to add though. To make this...

I started working on a solution. It should actually be pretty easy using the [axios Interceptors ](https://medium.com/swlh/handling-access-and-refresh-tokens-using-axios-interceptors-3970b601a5da). It could be hacked together by just checking for a refresh token on...

that might be a more flexible solution... I was planning on implementing the Username & Password "refresh" and refresh flows as build in "Auth" handlers. It might be easy to...

@wuservices that's correct. oAuth2 flows are fairly trivial to setup, so it could be added easily... An equivalent example would look like this: ``` ts const getOAuthUrl = (scopes: string)...