323 custom rest headers#967
Conversation
|
I reviewed this PR quickly and I have some comments :
Another comment, not related directly to this PR : |
There was a problem hiding this comment.
Please use GitHub comments instead of commenting this kind of things directly into the code...
|
@yDelouis What do you mean by becoming messy? I do not know the REST part of AA, but for me we have different handlers. |
|
The method |
|
OK, i suspected that |
|
@yDelouis can you refactor this PR? |
|
After 4.0. |
|
Refactored to #1470. |
It seemed like some of the stuff under the contributions page didn't apply to this PR (I don't think I should be deploying new snapshots willy nilly for example), so I may have done this wrong.
I also manually checked the code that the tests output, but I would feel better if there were automated testing in place to be sure that headers were properly set.
Lastly, I think this code will break if there is both a @RequiresHeader and a @Header annotation on the same method. Users would have to be pretty dumb to do this, but it is definitely a thing that is conceivable.
Let me know what you all need in the way of support for this.