John Backus

@MastaAaron THANK YOU. I was debugging the alias plugin + SVGr + rollup for like 2 hours and your tip about relative paths finally helped me fix my problem

@tarcieri Ok so the issue in my case was that we have an integration test like this: ``` ruby # creating the resource response1 = client.post(...) # getting the resource...

@tarcieri I think that sounds surprising to me because my impression of HTTP.rb was that it aimed to provide an immutable and chainable interface for performing requests. While I agree...

At the very least it would be nice if I could have something like `response.finalize` that I can call and get a simple immutable response wrapper that isn't tied to...

Would it introduce performance implications and/or breaking changes if each response object had a separate connection object?

Also thank you @ixti that is helpful

Thanks for opening this issue and fixing the problem so quickly @dreid! We ran into the same issue and actually spent some time bugging datadog support. We sent them this...

I'd be open to something like that (ideally not a totally new cop). I don't use scenarios so I probably wont implement that in my free time but if you...

This is actually an issue for many of our cops (and I haven't been sure how to improve rubocop-rspec to fit the various use cases) so how do you feel...

I'd rather just define the globs. It would be extremely hard to statically determine the types for different specs.