Why does URI.fragmentQuery not return URI

[ooxi]

Hi,

would it be possible for URI.fragmentQuery to return URI instead of a {}?

That way one could require(['URI.fragmentQuery'], function(URI) {}) instead of having to require both URI and URI.fragmentQuery.

-- ooxi

[rodneyrehm]

My goal is to drop the fragment plugins and replace them with URI.fragment(true) always returning a URI instance - see #129.

I'm not sure if I can do this in 1.13.0 or have to go 2.0.0 according to semver. I would prefer the former, but this could be considered a break in API conformance.

When that change lands, both plugins would be removed and this request would be void.

[ooxi]

I'm not sure I understood what URI.fragment(true) should do? If you change the plugins to fragmentQuery / fragmentUri instead of overloading fragment I think you would have to bump the version of the hole package.

But since this major API change seems to be not in the near future, would you consider changing the return value of the fragment plugins in a minor version?

[ooxi]

Thanks!