We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The docs suggest nesting any extra params under a custom key, in signed tokens. https://docs.mux.com/guides/secure-video-playback#passing-custom-parameters-to-a-signed-token
custom
{ "sub": "{PLAYBACK_ID}", "aud": "{AUDIENCE_TYPE}", "exp": "{EXPIRATION_TIME}", "custom": { "session_id": "xxxx-123" } }
But the type of params field in the MUXJWTSignOptions does not allow this, necessitating the use of ts-ignore if custom parameters are being used.
params
MUXJWTSignOptions
mux-node-sdk/src/util/jwt-types.ts
Line 43 in 5b63e5b
Maybe this can be expanded to something more relaxed like params?: Record<string, string | Record<string, string>>; ?
params?: Record<string, string | Record<string, string>>;
Not the most severe bug but would be a nice QOL improvement.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The docs suggest nesting any extra params under a
custom
key, in signed tokens. https://docs.mux.com/guides/secure-video-playback#passing-custom-parameters-to-a-signed-tokenBut the type of
params
field in theMUXJWTSignOptions
does not allow this, necessitating the use of ts-ignore if custom parameters are being used.mux-node-sdk/src/util/jwt-types.ts
Line 43 in 5b63e5b
Maybe this can be expanded to something more relaxed like
params?: Record<string, string | Record<string, string>>;
?Not the most severe bug but would be a nice QOL improvement.
The text was updated successfully, but these errors were encountered: