-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
fix: return the shortest, completely resolved path in the resolve command #5704
Conversation
Blocked on ipfs-inactive/interface-js-ipfs-core#385. |
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.
Yeah, this is a rather breaking change but I don't know if there is a better way other than adding a check for rp.Remainder() == ""
Closing in favor of just restoring existing behavior (for now). |
1f11184
to
4fe3a72
Compare
…mand fixes #5703 License: MIT Signed-off-by: Steven Allen <steven@stebalien.com>
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.
The only nit I have is using the +
operator over some path specific function (either go-path
or path
's Join()
)
However, I question the necessity for it here outside of being pedantic. Maybe we should be though.
@djdv let'd tackle that in a followup PR (the current code was already doing that). |
fixes #5703
This is a breaking change. We used to return an error if the path didn't end at a CID but, IMO, that's incorrect. We should allow resolution of paths that stop in the middle of an object.