Barney Carroll

@JamesMGreene this is probably too little far too late, but I'm wondering if the following interfaces would have solved your problem: ``` javascript function fragmentQuery( input ){ return URI( URI(...

@JamesMGreene I'm glad you have moved on to better (I hope!) problems ;) @rodneyrehm I think this issue should be closed – without a clear requirement & stakeholding owner it's...

**tl;dr:** I don't think URIjs should explicitly cater for fragment abuse on an API level; I'm not even using my fork (I use the code demo'd in those snippets explicitly...

Sure thing. For the sake of focus, are we saying that the current API (for fragment abuse) is up for a total re-write? Obviously I'd like things to stick to...

@rodneyrehm there's another project I'm a big fan of – [Sinon.js](http://sinonjs.org/) – that has similar issues to what URIjs is facing: outdated and fragile modularization methods, constant hotfixes and support...

As far as I see it there are 3 possible first steps: 1. Create a `modular` fork (and wait for merges to become a full-time job ;) 2. Create a...

Personally, I always try to modify URIs using intermediate objects. Of course it would be more memory efficient and certainly terser to be able to perform the task using a...

Completely misunderstood your original query, @gansbrest – that's what I thought you wanted. So all you actually care about is the position of the attribute. Why do you need the...

- [x] No - [x] Done - [ ] Todo

Slot mechanism currently only allows one level of egress. Is this a blocker? 🤔