Skip to content

GraphQL Client adoption: Code browsing

Created by: umpox

Plan

We’re looking to increase adoption of Apollo Client across code browsing components.

The aim of this issue is to identify and eventually improve areas that:

  • Would benefit from serving cached data. High-traffic areas where data is unlikely to change whilst the user is on the page.
  • Would benefit from refactoring data fetching logic into a shared API. Some examples may be complicated RxJS code that could be abstracted, or usage of FilteredConnection that has proven difficult to modify previously.

Useful resources

Please use this issue to discuss and identify these areas. Will create follow-on tickets to track implementation.

Tracked issues

@unassigned

@courier-new: 1.00d

Completed: 1.00d

@gitstart-sourcegraph

Completed

@tjkandala

@umpox

Completed

@valerybugakov

Completed

@vovakulikov: 5.00d

Completed: 5.00d

Legend

  • 👩 Customer issue
  • 🐛 Bug
  • 🧶 Technical debt
  • 🎩 Quality of life
  • 🛠Roadmap
  • 🕵Spike
  • 🔒 Security issue
  • :shipit: Pull Request