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

encoded-option in @Param annotation does nothing? #1087

Closed
MartinDevillers opened this issue Oct 2, 2019 · 3 comments · Fixed by #1138
Closed

encoded-option in @Param annotation does nothing? #1087

MartinDevillers opened this issue Oct 2, 2019 · 3 comments · Fixed by #1138
Assignees
Labels
bug Unexpected or incorrect behavior feedback provided Feedback has been provided to the author

Comments

@MartinDevillers
Copy link

I believe the encoded option in the @Param annotation does nothing. Regardless whether I set the value to false or true, my input is always encoded again (which in my use case is undesirable).

Browsing around this repository, I can see the value being read in the Default implementation of the Contract interface, and then being added to the indexToEncoded variable in the MethodMetadata class. But, from there I cannot find any code that actually reads this value.

boolean encoded() default false;

data.indexToEncoded().put(paramIndex, paramAnnotation.encoded());

public Map<Integer, Boolean> indexToEncoded() {

@kdavisk6
Copy link
Member

kdavisk6 commented Nov 3, 2019

@MartinDevillers

encoded has been maintained for backward compatibility and should be deprecated. We no longer need it as values that are already pct-encoded should be identified during expansion and passed through without any changes. #1096 does indicate that there are some cases where we are not correctly identifying provided pct-encoded values. I'll relate these two for investigation.

@kdavisk6 kdavisk6 added the bug Unexpected or incorrect behavior label Nov 3, 2019
@kdavisk6
Copy link
Member

We have marked this as parameter deprecated for now. We will continue to look into a fix for 10.7

@kdavisk6 kdavisk6 added the feedback provided Feedback has been provided to the author label Nov 15, 2019
@kdavisk6
Copy link
Member

As noted in #1108, the encoded property has been deprecated. In addition #1138 corrects our issues detecting fully and partially encoded values.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected or incorrect behavior feedback provided Feedback has been provided to the author
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants