Skip to content
New issue

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

Missing type for cacheKeyBuilder #547

Open
sortxyz-admin opened this issue Feb 7, 2025 · 1 comment · May be fixed by #546
Open

Missing type for cacheKeyBuilder #547

sortxyz-admin opened this issue Feb 7, 2025 · 1 comment · May be fixed by #546
Labels
bug Something isn't working

Comments

@sortxyz-admin
Copy link

The type info for the new cacheKeyBuilder option is missing.

@aheckmann aheckmann linked a pull request Feb 7, 2025 that will close this issue
Copy link

dosubot bot commented Feb 7, 2025

Hi @sortxyz-admin! I'm a bot here to help you with bugs, questions, and becoming a contributor while you wait for a human maintainer.

The cacheKeyBuilder function in the fast-jwt codebase is expected to take a token as input and return a value that can be used as a key in the cache. While the specific data types for the input and output are not explicitly defined in the codebase, it is typically inferred that the input is a string (the token), and the output is a string or hash suitable for use as a cache key [1].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot dosubot bot added the bug Something isn't working label Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant