Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Caching #29

Open
stefanvanburen opened this issue Apr 6, 2024 · 1 comment
Open

Caching #29

stefanvanburen opened this issue Apr 6, 2024 · 1 comment

Comments

@stefanvanburen
Copy link
Owner

Ideally, we'd cache our results so that we don't have to hit the network as often.

Probably the best way to do this would to be to understand the buf command cache structure, but OTOH because we aren't directly executing commands via buf, we're going to get results that aren't written there.

Another approach is to just keep an in-memory cache, since for the most part we're viewing immutable contents - commits are immutable, and currently neither owners or modules can be renamed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant