cube-js/cube

How can I perceive the token-expired situation?

Open

#3,862 opened on Dec 29, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Rust (19,563 stars) (1,965 forks)batch import
help wanted

Description

If the token is expired, I will get an error with HTML message filled: <span data-ansi-line="true"><span>Not authorized</span></span>. I use WebSocketTransport and QueryRenderer in my react app.

The problem is: I need to handle the token-expired(or invalid) situation (maybe to renew a token or logout user). But I can not find any way except to use error.toString().match(/Not\sauthorized/). It's not robust.

Is there any other way?

Contributor guide

Tech stack
javascripttypescriptreact
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic knowledge of Cube.js clientReact
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The issue requests a built in mechanism to detect token expiration in Cube.js's WebSocketTransport and QueryRenderer. Currently, users must parse error messages. A potential solution is to add an event emitter or callback (e.g., onTokenExpired) that provides a structured error. Relevant files include WebSocketTransport.js and QueryRenderer.js in the cube js client package. Maintainers may have discussed alternatives in the comments.
How can I perceive the token-expired situation? · cube-js/cube#3862 | Good First Issue