By default, only run specs not labeled as “future”.
The tag now handles a failure in rendering by outputting the error as an HTML comment. I’d like a better way.
The tag now handles failure downloading the gist.
I think I’ve configured VCR and WebMock correctly.
It looks like we can correctly serve up a gist, as long as nothing goes wrong.
We can correctly serve up a gist even if we don’t specify the filename, as long as there’s only one file.
Learned some surprising things about URI.join() as it relates to constructing the correct gist URL.
We can correctly handle an error code, but perhaps over-estimate what represents an "error".
We now limit interpreting an HTTP response as an "error" if the code is in the 400s or 500s.
Added a placeholder to check a 300s HTTP status code.
Began switching HTTP clients from HTTParty to Faraday, at Twitter’s insistence.
Switched all the tests from HTTParty to Faraday.
Goodbye HTTParty and webmock; we hardly knew ye.
Cleaned up a bit.
Found what looks like a mistake in VCR. Saff Squeeze time.
Figured out that I never used Faraday correctly. I don’t know how any of this ever worked. Fixed.
Removed obsolete code.
Now all paths check the same code; time to remove duplication.
Moved the production code up one level of the call stack.