Bob Aman
Bob Aman
This no longer gives an error in the 3.0 release branch, however, it also does not do what you'd probably expect. Since `query_values` does not (and will not) provide indifferent...
See also #94.
Actually, I don't feel that this is a duplicate issue.
However, I think the URI template spec doesn't define what behavior should be here. I think this should actually be an `ArgumentError`, TBQH.
This has occasionally come up. I think this is a perfectly reasonable usage of Addressable. We have a number of freeze tests already in the test suite, but clearly it's...
https://tools.ietf.org/html/rfc3986#section-2.5 applies here. > When a new URI scheme defines a component that represents textual data consisting of characters from the Universal Character Set [UCS], the data should first be...
We should probably add a test case for `uri.query_values = {"À": "ア"}` since it's a cited example.
These are some gross URIs. 😝 That said, I'm not sure I think this is a bug. Given what `display_uri` is supposed to do, this is legitimately an exceptional condition....
As a matter of implementation, I agree that this should be a peer method to `parse`. As a matter of practicality, I think this would produce a massive maintenance load...