yeah, I know, this is silly to put in a commit, but meh
Object.keys doesn’t work in older browsers, adding in a util function for it, thanks to Marcelo Pereira de Oliveira for the fix
always use ‘var’
adding in handlers for empty arrays and objects when it makes sense
just a note in case this needs improvement
Function.prototype.bind polyfill to handle old browsers, this should be sufficient but just in case we can use the real polyfill
if warnings or errors are present, colour the open/close buttons accordingly and open the toolbar so people can’t miss it!
RESPECT THE CHAOS MONKEY!
be a little more accurate, these aren’t just jQuery issues
should be nice to IE, it can’t help being a crappy browser
When loading request and sub request data, try to be nicer. This means that if at first we don’t succeed, we wait and try again. If at second we don’t succeed, we wait longer and try again, and … you get the idea. This also tries to be un-intrusive about the handling this in the UI so as not to distract the developer with issues in the debugger.
do not re-use the storage serializer, it may not always be JSON and we need JSON here since we are communicating with the browser
be lax about our JSON, basically let anything through (see comment for details)
just do the < max retries, not <= the max retries
need an event for when the request actually fails, so that we can update the UI
clean up temp directories and stop sharing them across tests
add in load_all_subrequest_results_modified_since to the storage layer (and tests)
clean up the App::Debugger so that it is easier to extend, also remove the { data => …, links => … } stuff as we are not using it, then adding tests
make the tests clean up after the run (and before, in case of a bad run)
allow fetching of subrequests ‘modified-since’ through the App::Debugger as well