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
In the README there is a concept of allowing different types of filters. I dig that but I would love to see how it would look to have the filter param be part of the path components for the URI.
Challenge: allow for any filter to be appended to the end of the host:port components on the URI.
BONUS: allow for some known resources to be short-handed or variants that resolve to the known good filter.
In the README there is a concept of allowing different types of filters. I dig that but I would love to see how it would look to have the filter param be part of the path components for the URI.
Challenge: allow for any filter to be appended to the end of the host:port components on the URI.
BONUS: allow for some known resources to be short-handed or variants that resolve to the known good filter.
http://foo/StickAndPuck
http://foo/stick_and_puck
http://foo/stickPuck
http://foo/stick_n_puck
should all return the exact same results.
Have fun!
~Leon
The text was updated successfully, but these errors were encountered: