replace AddAsk with SetAsk, to convey intent #275
Merged
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.
Why does this PR exist?
Searching for a
DeleteAsk
operation caused me to go down the rabbit hole of trying to figure out how asks added with theAddAsk
method could be replaced with a new ask (when the miner changed their minimum piece size, for instance).As it turns out, the current implementation of go-fil-markets allows a storage miner to have exactly one ask, manipulated through the misleadingly-named
AddAsk
method.What's in this PR?
This PR replaces the
AddAsk
method with aSetAsk
method, and replacesListAsks
withGetAsk
.Alternative approaches
If a
SignedStorageAsk
had an identity (I don't see that it does right now), we could preserve theAddAsk
andListAsks
signatures. We'd need to add aDeleteAsk
method, though.