chore: simplify 'get repo' API implementation #20348
Merged
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.
The repository
Get
endpoint currently normalizes, sanitizes, and augments the repo object with the connection status.But that work is already done by the call to
s.ListRepositories
.For normalization and sanitization, the duplication is a drift risk, but isn't otherwise a problem.
The extra connection status check shouldn't be a huge problem, because it's cached. But it'll duplicate the check when anyone clicks "refresh" in the repo list UI.
I've added unit tests to confirm that
Get
still gets the normalized, sanitized, and augmented repo object. I've confirmed that, if I remove those behaviors from the ListRepositories function, the tests fail (so we would catch a regression).