Linking to Repos in App

[BrianLitwin]

Do you all think it would be a good idea to intercept links to repos in repository ReadMe's and open a RepositoryViewController instead of re-directing the user to Github.com? Eg when a user clicks the Apollo Codegen link in GitHawk's ReadMe? There's already a workflow in place that we use for shortlinks, seems like it would be a matter of writing a regex and wiring it up.

[BrianLitwin]

for further clarification:

instead of opening repo links in safari:

we could open the links in GitHawk:

[rnystrom]

@BrianLitwin yes! that would be great

[BrianLitwin]

@rnystrom @Huddie After the user clicks a repository link, we gotta go grab the defaultBranchRef + hasIssuesEnabled info from graphql before opening the RepositoryViewController... I'm currently throwing a spinner here... lmk y'alls thoughts or if you have a better idea of how to keep the UI interactive while this quick fetch happens -->

The reason I use a .largeWhite spinner instead of a smaller one like we use elsewhere is because we are overlaying the spinner on top of text, ie for visibility. Most of the other places we use spinners they are against a white background.

[Huddie]

Cool stuff! The spinner seems different from the regular one which Idk how I feel about. I get that throwing a spinner on the view could get lost in the text and that’s why you prob opted to go with a spinner with a background view behind it.
Maybe open repositoryViewController right away and have it load then? So it’s empty with the regular spinner rather than waiting on the previous page for the load.

Kind of link how the redirect works currently. Opens safari right away and then loads the webpage.

_{Sent with GitHawk}

[rnystrom]

Ya I almost think adding the ability to init a new repo VC without a branch would be good. Make it optional and the VC fetches it?

_{Sent with GitHawk}

[Huddie]

^^ yup

_{Sent with GitHawk}

[BrianLitwin]

@Huddie @rnystrom .. I'm fine with that.. only caveat is that after fetching the graphql info, graphql could return an error or "repo not found" and the process would like:

• user taps link
• segue to empty repo view controller
• fetch repo info
• fetch fails
• segue to safari view controller

An example of that is with our Apollo-codegen link.. the repo was renamed and GraphQL responds with "repo not found"

I think the empty vc approach is still the right move, just have to make it seamless if loading the repo fails.

[j-f1]

You could present the Safari VC as a modal with a fade, then pop the repo view controller without animation once the Safari VC is completely visible.

[Huddie]

🤔 maybe an alert saying “repo not found, try opening in web” with a button that when clicked will redirect you? Or I guess you could just redirect them 🤷‍♂️

_{Sent with GitHawk}

[rnystrom]

@BrianLitwin so V3 handles the rename but GraphQL doesn't?