Do you have a timeline for when the new functionality will be available in the JS SDK?
It is indeed the JS-SDK. The culprit can be found here: https://github.com/cognitedata/cognite-sdk-js/blob/964d5ab1539226c7d383e9d07910ee096adbc4df/packages/core/src/credentialsAuth.ts#L52
For practical reasons I would like access to CogniteClient outside of React. What is the recommended way of achieving this while maintaining a single source of truth for authentication?Edit: Nvm… It was just the first 401 that was tripping me up. .authenticate() fixed it.
It’s looking really good. Made my job a lot easier. I created an issue on the repository. Nothing breaking, but I had to make a small workaround.
Did exactly what I needed. Thank you :)
Haven’t had a chance to implement it yet. I’ll let you know as soon as possible :)
Awesome! I’ll try it out!
We have the error-boundary in place in our React-application, but it does not deal well with async-errors outside of React-code. You can in theory rethrow the error-messages and have them caught, but I couldn’t get this approach to work.Also I would very much like not having to try-catch every single api-call we make.I couldn’t find anything in the documentation that seemed relevant. Which part would you have me look at?
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
