Backup/restore the collections, history, config and hintmap JSONs located at ~/.scout to a gist specified by the user.

Usage

1. Add the following property to ~/.scout/config.json:

   sync: {
     "token": "{access_token}",
     "gist": "{gist_id}"
   }

2. Create a new GitHub personal access token which has the gist scope.

3. Copy the access token and replace {access_token} with it.

4. Create a new gist and save it.

5. Copy the gist id (last part of the URL, after the username) and replace {gist_id} with it.

The HistoryManager should ignore a HttpEnvelope that has no address/method.

• Format the server response body depending on the data type: JSON, XML, URLEncodedParams, etc.
• Use CodeMirror or something similar to highlight the syntax of the response body (in Raw format)

Provide an option to keep and show each of the responses when HTTP 3xx redirects are followed.

• Rewrite the application menu and provide a unified mechanism for command execution
• Clean up the window management API

Users can create variables, assign them values and use them in the HTTP headers.

• Add an indicator to mark tabs within the same domain
• Add another indicator to show the status of the response (or a loader if Scout is waiting for a response)
• Right click menu:
  • New Tab
  • Duplicate
  • Pin Tab
  • Send
  • Stop
  • Close Tab / Close Other Tabs
  • Reopen Closed Tab

Many HTTP headers accept a list of comma-separated values, e.g. Accept: application/json, text/xml.

Modify the autocomplete directive to support those kinds of lists (trigger a different autocomplete when the user types , or ;), and to avoid saving such a list as a single value in the hint-map.

Record and show the following information in the status bar:

• Server response time
• Returned HTTP Status Code
• Request/Response Size

Additional information for each status can be provided if the user requests it (e.g. explanation of the status code, or the size of the different request/response parts, etc.)

Support dynamic computation of values:

• compute hashes
• generate GUIDs
• apply timestamps
• randomize data for testing

• Save individual requests (w/o the server response)
• Group requests into collections
• Create multiple snapshots of a HTTP communication (keep the server responses under a request in the collection)