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
ipfsproxy: use PinPath to match IPFS behaviour #690
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, except two comments
@@ -55,8 +55,8 @@ func (rpcapi *RPCAPI) PinPath(ctx context.Context, in *api.PinPath, out *api.Pin | |||
} | |||
|
|||
// UnpinPath resolves path into a cid and runs Cluster.Unpin(). | |||
func (rpcapi *RPCAPI) UnpinPath(ctx context.Context, in string, out *api.Pin) error { | |||
pin, err := rpcapi.c.UnpinPath(ctx, in) | |||
func (rpcapi *RPCAPI) UnpinPath(ctx context.Context, in *api.PinPath, out *api.Pin) error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can unpin utilize pinOptions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it doesn't, but for parallelism (allows using same code to call pin/unpin) and if at some point in history we can unpin with options it's marginally better this way.
f81edea
to
e4cd17b
Compare
License: MIT Signed-off-by: Hector Sanjuan <hector@protocol.ai>
0574ea8
to
23db807
Compare
License: MIT
Signed-off-by: Hector Sanjuan hector@protocol.ai