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
With spring-mvc (and other frameworks) it is easy to handle requests where one parameter is used more than once in a single request, such as GET http://my-url.org/my-service?param=value1¶m=value2¶m=value3. (For instance, using spring-mvc one could use a List for a single parameter with multiple values or a MultiValueMap.)
However, the TraversalBuilder and Hop classes of spring-hateoas store template parameters in a Map and thereby fail to handle the above situation. Could this change, so that clients can handle multiple values?
The text was updated successfully, but these errors were encountered:
If this Map<String, List<String>> refers to the collection of all parameters and their possible multiple values, then yes, that seems to be a way of doing what I mean.
With spring-mvc (and other frameworks) it is easy to handle requests where one parameter is used more than once in a single request, such as
GET http://my-url.org/my-service?param=value1¶m=value2¶m=value3
. (For instance, using spring-mvc one could use a List for a single parameter with multiple values or a MultiValueMap.)However, the TraversalBuilder and Hop classes of spring-hateoas store template parameters in a Map and thereby fail to handle the above situation. Could this change, so that clients can handle multiple values?
The text was updated successfully, but these errors were encountered: