-
Notifications
You must be signed in to change notification settings - Fork 12
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
Ability to specify cutsom keys (or paths) #37
Comments
Is this different from your previous question (#35 )? The main idea for me was to use the path of the api request as a "group" and the "slug" or the last segment of the request as the item key. We could image a configuration option that would allow to use the full path as key. Let say now I have an api living at This setting would generate a group key Therefore we could imagine an option What do you think? |
Thanks for the reply, Yes that would work, Although I would think the domain inclusion is not common, but the ability to add data that would be part of the key would be valuable. It would seem that a switch something like |
That makes sense. I agree the custom key would be a nice addition. Would you have time to do a pull request? With an example of the earlier hook? |
I have a use case where my app responds to multiple domains.
As such the cache returns the same data for
/somepath/someId
for each of the domains. Is there a way to specify custom keys so I can add my own key in? perhaps in some before hook?The text was updated successfully, but these errors were encountered: