You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juneau.apache.org by James Bognar <ja...@apache.org> on 2018/06/28 14:53:06 UTC
Remove @QueryIfNE/@FormDataIfNE?
This question is aimed primarily at Steve Blackmon since Streams uses these
annotations.
With the recent work for combining the REST server and client annotations
into a single set of annotations, I'd like to remove the @QueryIfNE
and @FormDataIfNE annotations. The @Query and @FormData annotations have
many more Swagger-related fields now and I don't want to have to duplicate
them on the *IfNE annotations as well.
If you were using *@QueryIfNE(name="foo")* or *@QueryIfNE("foo")* before,
it would be replaced with *@Query(name="foo", skipIfEmpty=true)*.
Thoughts?
Re: Remove @QueryIfNE/@FormDataIfNE?
Posted by Steve Blackmon <st...@blackmon.org>.
No objection.
Sent from Astro <https://www.helloastro.com> for Mac
On Jun 28, 2018 at 9:53 AM, James Bognar <ja...@apache.org> wrote:
This question is aimed primarily at Steve Blackmon since Streams uses these
annotations.
With the recent work for combining the REST server and client annotations
into a single set of annotations, I'd like to remove the @QueryIfNE
and @FormDataIfNE annotations. The @Query and @FormData annotations have
many more Swagger-related fields now and I don't want to have to duplicate
them on the *IfNE annotations as well.
If you were using *@QueryIfNE(name="foo")* or *@QueryIfNE("foo")* before,
it would be replaced with *@Query(name="foo", skipIfEmpty=true)*.
Thoughts?