feat: support prev caveat in store/list and upload/list
#137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this implements support for the `prev` caveat proposed in storacha/w3up#423 I'm not sure the semantics are right yet, deploying to get a test env to play with
View stack outputs
|
|
closing for now per comment in storacha/w3up#423 (comment) - going to investigate a different direction for this |
|
Reopening as explained in storacha/w3up#423 (comment) and storacha/w3up#423 (comment) |
|
This is blocked on the update to Can you send a PR to https://github.com/web3-storage/specs/blob/main/w3-store.md#storelist 🙏 |
|
closing so I can open a new PR to redeploy infrastructure |
and use it to implement support for the `pre` caveat in `store/list` and `upload/list`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this implements support for the
prevcaveat proposed in storacha/w3up#423I'm not sure the semantics are right yet, deploying to get a test env to play with