Ken Beaudin

I would make adjustments to the following: "What would you like me to accomplish for the company in the 3months, six months, and a year? How much value do you...

Proposal 1 Adding accountType on the JWT Token pages/api/[...next-auth].js ``` async jwt({ token, account, profile }) { // Persist the OAuth access_token and or the user id to the token...

Solution 2 As a work around to being unable to make MongoDB calls from the middleware.js file: middleware.js Make a request to Next.js API end point and include in the...

The current naming convention is confusing and it will be remedied in the solution we propose. (session is actually JWT token). ```js const session = await getToken({ req: req, secret:...

This error populates in the build: `file:///home/travis/build/ccxt/ccxt/js/src/test/test.js:12 throw new Error(exceptionMessage(e)); ^ Error: [Error] Error: [Error] Error: ENOENT: no such file or directory, open '/home/travis/build/ccxt/ccxt/js/src/test//../../.././ts/src/test/static/markets/huobi.json' at Object.openSync (node:fs:603:3) at Object.readFileSync (node:fs:471:35)...

@olegtaranenko I've noticed that. I'm working on the remainder of the public and private spot functions now using Binance has examples. More contributions coming soon.

Is there a reason why this bug fix is not getting approved?

@thernstig Wouldn't it make more sense to create a new module, with a name distinct from RFC822, to implement this "slight difference"? This would help avoid confusion or potential issues...

Great job on fixing the bug! To ensure this fix is robust and won't break in the future, could you add a test that covers this scenario? For example: ```...