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
Currently ataraxy only supports destructuring route parameters into a vector; often I find myself having to translate these parameters immediately into a map so I can attach specs to their keys and not have to remember a specific ordering.
It would be nice if ataraxy supported the following mapping, allowing parameters to be bound into a map.
["/path" #{foo bar ?baz}] [:foo/handler {:foo foo, :bar bar, :baz baz}]
One difficulty is that we'd have to decide what to do with optional parameters. It seems there are two options, either:
the parameter ?baz is bound in the map to the kv pair of :baz nil, or...
the key :baz is not put in the map at all.
Personally I think that 2 is the better approach, but it might be counter to peoples expectations.
The text was updated successfully, but these errors were encountered:
Currently ataraxy only supports destructuring route parameters into a vector; often I find myself having to translate these parameters immediately into a map so I can attach specs to their keys and not have to remember a specific ordering.
It would be nice if ataraxy supported the following mapping, allowing parameters to be bound into a map.
One difficulty is that we'd have to decide what to do with optional parameters. It seems there are two options, either:
?baz
is bound in the map to the kv pair of:baz nil
, or...:baz
is not put in the map at all.Personally I think that 2 is the better approach, but it might be counter to peoples expectations.
The text was updated successfully, but these errors were encountered: