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

Add the store.get capability to the @storacha/client API #245

Closed
fforbeck opened this issue Jan 6, 2025 · 2 comments
Closed

Add the store.get capability to the @storacha/client API #245

fforbeck opened this issue Jan 6, 2025 · 2 comments
Assignees

Comments

@fforbeck
Copy link
Member

fforbeck commented Jan 6, 2025

About 3 months ago, the console project was updated to use client.capability.blob.get(shard.multihash) from the @storacha/client.

As a result, the w3ui was also updated to use @storacha/client instead of w3up-client.

Additionally, a fallback strategy was added to the Console App to call client.capability.store.get(shard) if blob.get fails for any reason.

However, I recently released a new version of the @storacha/client and noticed that the store capability is no longer present in it — meaning the fallback strategy in the Console App won’t work anymore.

If we decide to use the @storacha/client in the Console App, we need to make sure it handles the store.get somehow, otherwise, we won't be able to fetch old content (uploaded before the blob protocol).

@alanshaw
Copy link
Member

alanshaw commented Jan 15, 2025

@fforbeck we agreed to use w3up-client in w3ui until the store protocol was officially deprecated and removed. I think we can close?

I will add a task in the Store Protocol deprecation plan to handle migrating items stored using the store protocol to blob protocol. i.e. allowing folks to still list/remove items added via store protocol.

@fforbeck
Copy link
Member Author

Yes. Absolutely. Let's close this one.

@github-project-automation github-project-automation bot moved this from Sprint Backlog to Done in Storacha Project Planning Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants