… targeted GET requests for new rows. We use the available information in the socket message to update the relevant row (if visible in the list).

… sources list

…a job status update message comes across the websocket. We now use data exclusively from the websocket to update the UI.

… templates list. List is solely updated based on data from the websocket messages.

…e need to stick with a single spelling of the word

… to update the relevant row in the templates list.

…vant job row. Also adds logic to attempt to re-order the list when the sort order is -finished since we have enough information client-side to do that.

…ebsocket message

…t messages

…own the line by buildTooltips().

…t and populated in the object.

For anyone reading this later, know that AdHocCommands still have unified_job_template and unified_job_template_id fields, they are just nonetypes because they don't get used by the AdHocCommand objects. Which means you have to actually get the object, not just check that it's there, to use it the way I am in this change.

…long with successful/failed/canceled

… the API.

…d then breaking the DateTime function