You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, path parameters are self-explanatory. However it is useful under certain circumstances or for verbosity to have each path parameter documented.
Currently the matching @param only shows up in the "API Example:" section. It would be great if a "Path Parameters:" section was added alongside the "Input:"/"Output:"/"Query parameters:"/etc. sections.
Note, the string name of the parameter inside @PathParam (ie: @PathParam("foo")) should just be for display purposes so java variables can be named whatever is appropriate.
The text was updated successfully, but these errors were encountered:
Originally we had it there, but we moved it up because someone preferred it up. We can definitely make this optional, but I won't have time to do this right away. Patches welcome :)
Usually, path parameters are self-explanatory. However it is useful under certain circumstances or for verbosity to have each path parameter documented.
Currently the matching @param only shows up in the "API Example:" section. It would be great if a "Path Parameters:" section was added alongside the "Input:"/"Output:"/"Query parameters:"/etc. sections.
Note, the string name of the parameter inside @PathParam (ie: @PathParam("foo")) should just be for display purposes so java variables can be named whatever is appropriate.
The text was updated successfully, but these errors were encountered: