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
Could radix3 support multiple parameters in a single node? The main use case is to represent a composite key in a URL.
For example: /patient/:name,:dob.
From RFC 3986
Aside from dot-segments in hierarchical paths, a path segment is considered opaque by the generic syntax. URI producing applications often use the reserved characters allowed in a segment to delimit scheme-specific or dereference-handler-specific subcomponents. For example, the semicolon (";") and equals ("=") reserved characters are often used to delimit parameters and parameter values applicable to that segment. The comma (",") reserved character is often used for similar purposes. For example, one URI producer might use a segment such as "name;v=1.1" to indicate a reference to version 1.1 of "name", whereas another might use a segment such as "name,1.1" to indicate the same. Parameter types may be defined by scheme-specific semantics, but in most cases the syntax of a parameter is specific to the implementation of the URI's dereferencing algorithm.
Additional information
Would you be willing to help implement this feature?
The text was updated successfully, but these errors were encountered:
stuft2
changed the title
Multi-parameter support
Radix node with multiple parameters
Feb 22, 2023
Hi thanks for issue and rfc reference. Let's track this via It is related to #11 we need to support combining multiple static/dynamic params in same segment.
Describe the feature
Could radix3 support multiple parameters in a single node? The main use case is to represent a composite key in a URL.
For example:
/patient/:name,:dob
.From RFC 3986
Additional information
The text was updated successfully, but these errors were encountered: