mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 20:11:54 +00:00
0316dbc2e1
In our backend, we mostly follow the convention that type names for the resolvers match up with the types in the GraphQL API, with the extra `Resolver` suffix. However, this is broken by the `GitTreeEntryResolver` where there were no types called `GitBlobResolver` or `GitTreeResolver`, since all functionality was implemented on top of `GitTreeEntryResolver`. Since Go supports implicit method forwarding for embedded structs, I think we can improve the code consistency & readability by adding these two stub resolver types. As struct embedding is not a super common pattern, I've explicitly mentioned that in the doc comments for `GitBlobResolver` and `GitTreeResolver`. |
||
|---|---|---|
| .. | ||
| background | ||
| lsifuploadstore | ||
| ranges | ||
| resolvers | ||
| trie | ||
| BUILD.bazel | ||
| db.go | ||
| noop.go | ||