allow a user to remove their token, via context menu and later options page

[dong-qian]

Should reset the access token request like first time install the extension.

[OleksiyRudenko]

Upd: moved the below to #5

Kudos to the plugin author. It's a great, really convenient alternative for browsing repo content.

I believe this might be linked so adding the case here.

When in private repository the progress spinner runs for a while and finally resolves to an error.

It is most likely to happen due to incompatibility of a token with current repo (for it is private).

Possible solution might be to fallback to the default (native) view of file list + optionally offer to add a token. The latter might also require multiple tokens support.

Besides one may not want to grant plugin a permission to read a repo due to organization info security policy requirements, so it might be even better to expose default view while plugin is busy with reading the repo. Still it is important to know it is working.

Please consider the following approach.

1. When there is no token in place (or no any tokens when multiple tokens supported), inject a prompt to add a token (no change in current implementation)
2. When there are any tokens:
   (a) expose default view + inject progress bar while plugin reads a repo (possibly trying a matching token)
   (b) on success remove the progress bar and replace the view, otherwise replace the progress bar with a warning (smth like "Failed to read a repo due to token expiration or access restrictions") and a prompt to add a token

[brumm]

@qiandongyq I'm sorry you were having issues!

For now you can switch to the extension's context in the console and call window.clearToken() to get back to the initial state. Here are some screenshots:

I'll add an entry to the extensions pop up menu to make this a bit more convenient until I add a full options page :)

[brumm]

Thanks for the report @OleksiyRudenko! Could you move this to another issue? Tako should work on private repos, so I'm not sure what surfaced this error (that I forgot to change to something more expressive ;))

[OleksiyRudenko]

@brumm done.
Please feel free removing or amending my comments in this issue at your discretion to keep the issue track clean.