-
-
Notifications
You must be signed in to change notification settings - Fork 435
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
Bug in the fix to 624 issue #632
Comments
Hi @orensolo thanks for following up so quickly. |
Hi @fenollp Thanks, |
Any progress on your side? I have this draft PR in the works: #634 |
My fix is not good. I am working to find another solution. I will update soon. |
Hi @fenollp I suggest replacing defaultContentParameterDecoder in req_resp_decoder.go with the following code:
This is similar to your fix. Just the condition to fallback the error is different (depends on the schema). Thanks, |
Hi,
There is a bug in the fix to #624 issue.
Using a special character in the parameter causes unmarshalling error.
Running the following:
Returns:
The fix assumes that there cannot be special characters in the input parameters - which is a wrong assumption.
The correct fix is to use the decodeStyledParameter instead of decodeContentParameter. (with some relevant changes)
Please change the fix to the following fix:
In validate_request.go:
And in req_resp_decoder.go, change decodeStyledParameter to the following:
Thanks,
Oren
The text was updated successfully, but these errors were encountered: