This repository was archived by the owner on Sep 20, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connected to #2263
In most files, the changes are adding a
GithubClient
parameter so that it can be passed to theLabelDetails
model, which is passed along to init and present aRepositoryIssuesViewController
.Also, I removed the RepositoryDetails parameter from the
RepositoryIssuesViewController
initializer and replaced it withowner
andname
. This was so that we didn't have to pass around a reference toRepositoryDetails
as well, and also because we were only using thename
andowner
fields ofRepositoryDetails
anyway.vid:
I've checked manually that it works when labels are embedded in other contexts as well. Only place it doesn't work is on the main RepoIssuesSectionController list, which as @Huddie suggested, we should enable as well.