Please be sure to read the contributor's guide to the GitHub package before submitting any pull requests.

Requirements

• Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
• Suggestion: You can use checklists to keep track of progress for the sections on metrics, tests, documentation, and user research.

Description of the Change

When the network is unavailable, the GitHub package behaves poorly:

• When starting or reloading Atom, the "log in to GitHub" view is shown from each Relay-backed view, which, of course, doesn't work.
• If the network becomes unavailable after Atom is already open, the next attempted network operation brings down the package hard with an uncaught exception.
• Relay actions that users explicitly initiate (like clicking on a refresh button, or triggering a mutation) uniformly create Atom error notifications, with customized messaging for the offline case.

I'm introducing:

• A special <QueryErrorView> case that recognizes network errors and offers to open the dev tools for more investigation. (Unfortunately, the errors thrown by fetch are TypeError instances with little information and a message of "fetch failed.")
• Create an alternate blank-slate case to show in place of the <GithubLoginView> when the network is unavailable.
• Ensure that further changes in network state are detected when offline so we can re-render again.
• Separate messaging for "offline" from "non-200, non-401 statuses"
• Handle the issueish tiles in the GitHub tab
• Preserve existing data and notify instead if a refetch fails, so you don't lose cached data.

Screenshots

When a user attempts to open a new item that uses Relay data (an issueish detail item, the reviews tab) while the network is offline, including items created during window state deserialization (like a reload):

When a user attempts to click a refresh button or perform a mutation while offline:

When the network dies in between the git fetch completing and the Relay refetch triggering somehow:

Alternate Designs

N/A

Benefits

Users on spotty wi-fi or airplanes can have a gracefully degraded Atom experience and informative error states.

Possible Drawbacks

The errors thrown by the fetch API are (deliberately, I believe) very vague. It's possible that we could report that a user is offline when they have misconfigured DNS or proxy settings, for example. The underlying OS network error is shown in the developer tools, but we have no way to read it.

Applicable Issues

Fixes #1844.

Metrics

N/A

Tests

I did manual testing both by toggling network connectivity in the dev tools and by actually disabling and enabling wi-fi.

Interestingly, the 'online' event that I'm using to auto-retry from an OfflineView doesn't seem to fire the first time you uncheck the "Offline" button in the dev tools, but it does every subsequent time. The event fired when I expected it to when the wi-fi was actually restored so I didn't investigate further.

Documentation

N/A

Release Notes

• The GitHub package reports clearer errors when no network connection is available.

User Experience Research (Optional)

N/A