-
Notifications
You must be signed in to change notification settings - Fork 42
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
@Cacheable on method with Guid as parameter seems not to work (Version: 1.0.7) #20
Comments
Can you try calling |
Yes, i just did that for the
So it is still correct but since the type has changed to
Do you see a way having the type of |
I reproduced your use case and it's indeed a bit tricky. However, isn't calling |
Sure, it's not the end of the world, but i don't want to change too much of my API, so this is a viable solution for now (which let's me keep my interfaces the same way):
Maybe you can make it work in a future version, if it is not too tricky... :) |
The issue is that pass the parameters through a |
I see, thanks for taking the time, much appreciated :) |
The example that is working fine (with id being a Guid.toString()):
Parameter {id} is resolved to:
If i know change the string parameter type to Guid like so:
In that case for some strange reason, the parameter ${id} that is passed to my api call is resolved to:
Any idea on what i might be doing wrong here?
NOTE: Without @Cacheable, the Guid type is working fine.
Thanks & Cheers!
The text was updated successfully, but these errors were encountered: