Support arbitrary float or int in URLs
- May 02, 2023
-
-
since `float` doesn't also catch `int` we don't want to encode every possible permutation (not that many, but the principle stands), just use `string` (default) and handle it later
-
-
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.
since `float` doesn't also catch `int` we don't want to encode every possible permutation (not that many, but the principle stands), just use `string` (default) and handle it later