This hook should use

repoClient.repoGetContents()

and receive the arguments listed here:

https://git.door43.org/api/swagger#/repository/repoGetContents

should return

{
  state: repoContents, isLoading, error
  actions: setRepoContents, getRepoClient
}

This hook should use

repoClient.repoGetRawFile()

and receive the arguments listed here:

https://git.door43.org/api/swagger#/repository/repoGetRawFile

should return

{
  state: repoFile, isLoading, error
  actions: setRepoFile, getRepoClient
}

Just to keep the track of work done in a collaboration week. A note from @klappy
I'm thinking we could start with some mock components, and then populate them later.

1. OrganizationsSelection
2. RepositoriesSelection
3. Branch/TagSelection
4. FilepathSelection

• For now we can just list a few mock strings for each in the selection.
• When we're done with the mock data, each component should do the fetching of the list of options via the corresponding DCS React Hook
• Each component should save the selection in the corresponding state the hook that we already created (or applcation state).
• Once organization, repository, branch/tag, and filepath are populated in the application state as strings, then we can generate the url strings.
• We should be able to reuse the components above to populate the old/new urls.

To simplify, we may be able to just handle one organization, repository and filepath. Then each side, old/new, gets to select branch/tag.
This limits the use case but is easier to implement and handles our most common use cases.

This hook should use

repoClient.repoListBranches()

and receive the arguments listed here:

https://git.door43.org/api/swagger#/repository/repoListBranches

should return

{
  state: repoBranches, isLoading, error
  actions: setRepoBranches, getRepoClient
}

This hook should use

repoClient.GetTree()

and receive the arguments listed here:

https://git.door43.org/api/swagger#/repository/GetTree
should return

{
  state: repoTree, isLoading, error
  actions: setRepoTree, getRepoTree
}

This hook should use

orgClient.orgListRepos()

and receive the arguments listed here:

https://git.door43.org/api/swagger#/organization/orgListRepos

should return

{
  state: orgRepos, isLoading, error
  actions: setOrgRepos, getOrgClient
}

Needs more documentation, particularly the auto-generated code.

It will be important that a developer can begin using this easily. They need to know what methods are available and what the parameters are.