Skip to content

Support arbitrary float or int in URLs

This MR fixes #20 (closed) by removing the numerical type matching for URLs, since float doesn't also accept int and we don't want to encode every possible permutation (not that many, but the principle stands), so, just use string (default) and handle it later.

Merge request reports