If I run Uri.parse("foo:bar#baz").removeFragment().toString(), I get "foo://:0bar?", where I'd just expect "foo:bar". This is particularly problematic for working with data: URIs, which aren't at all structured like typical hierarchical URIs and whose fragments must be ignored.
The text was updated successfully, but these errors were encountered:
It used the external getters for the existing port and query, which
are non-null even when the port or query are absent. This introduced
a new default-valued/empty part.
Also reordered declarations to have fields > constructors > rest.
Fixes issue #24593
BUG= http://dartbug.com/24593
R=asgerf@google.com
Review URL: https://codereview.chromium.org/1396973004.
It used the external getters for the existing port and query, which
are non-null even when the port or query are absent. This introduced
a new default-valued/empty part.
Also reordered declarations to have fields > constructors > rest.
Fixes issue #24593
BUG= http://dartbug.com/24593
R=asgerf@google.com
Review URL: https://codereview.chromium.org/1396973004.
If I run
Uri.parse("foo:bar#baz").removeFragment().toString()
, I get"foo://:0bar?"
, where I'd just expect"foo:bar"
. This is particularly problematic for working withdata:
URIs, which aren't at all structured like typical hierarchical URIs and whose fragments must be ignored.The text was updated successfully, but these errors were encountered: