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
It would be good to dynamically generate the cacheKeyPrefix based on the incoming request
The use case would be to set the cacheKeyPrefix to the tenantId for the incoming request so each tenant has its own namespace for the keys
For us the tenantId would either be in the header or as part of the JWT based on how the user is authenticated
The text was updated successfully, but these errors were encountered:
@Tam2 have you considered passing options to IdempotencyParams? you can also refer this test case.
node-idempotency/packages/core/tests/e2e/idempotency.spec.ts
Lines 70 to 105 in e6259d6
Sorry, something went wrong.
No branches or pull requests
It would be good to dynamically generate the cacheKeyPrefix based on the incoming request
The use case would be to set the cacheKeyPrefix to the tenantId for the incoming request so each tenant has its own namespace for the keys
For us the tenantId would either be in the header or as part of the JWT based on how the user is authenticated
The text was updated successfully, but these errors were encountered: