Skip to content

Add support to go directly to URL before API call#88

Merged
bswinnerton merged 2 commits intomasterfrom
go-directly-to-repo-before-api-call
Oct 29, 2017
Merged

Add support to go directly to URL before API call#88
bswinnerton merged 2 commits intomasterfrom
go-directly-to-repo-before-api-call

Conversation

@bswinnerton
Copy link
Copy Markdown
Owner

@bswinnerton bswinnerton commented Oct 29, 2017

As reported in #87, if you type the repository that you would like to go to without waiting for the GitHub API to respond, + Enter does not work.

This commit adds support to use + Enter to go directly to the repository before triggering an API call to fetch all of the account's repositories.

This is a little easier to review using GitHub's ?w=1 feature


Resolves #87.

As reported in #87, if you type the repository that you would like to go
to without waiting for the GitHub API to respond, <kbd>⌘</kbd> +
<kbd>Enter</kbd> does not work.

This commit adds support to use <kbd>⌘</kbd> + <kbd>Enter</kbd> to go
directly to the repository before triggering an API call to fetch all of
the account's repositories.
@bswinnerton bswinnerton self-assigned this Oct 29, 2017
@bswinnerton bswinnerton changed the title Add support go directly to URL before API call Add support to go directly to URL before API call Oct 29, 2017
@bswinnerton
Copy link
Copy Markdown
Owner Author

👋 @jasonrudolph, this should resolve your comment in #8 (comment) (and by relation, #87).

Unfortunately there's a catch 😕. The order of repositories that comes back from the GitHub API doesn't take into account the exact search term. So if you hit + Enter immediately after the repositories are shown in LaunchBar, you'll need to navigate down to your entry before hitting + Enter. I've opened #89 to explore ways of reordering the list of repositories so this doesn't happen.

@bswinnerton bswinnerton merged commit 5be308f into master Oct 29, 2017
@bswinnerton bswinnerton deleted the go-directly-to-repo-before-api-call branch October 29, 2017 19:11
@bswinnerton
Copy link
Copy Markdown
Owner Author

Unfortunately there's a catch 😕.

I've resolved said catch in #90 😄.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant