-
-
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: honour --ttl flag in 'ipfs name publish' #9471
Conversation
713cc21
to
6d118e2
Compare
1697988
to
6671993
Compare
f0b9e90
to
1db6669
Compare
e32eb1b
to
96414b9
Compare
0df0d8f
to
63fd9b2
Compare
63fd9b2
to
982ff1e
Compare
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.
@hacdias Thank you for fixing this and indulging my idea to implement ipfs name inspect
:)
I've bubbled up all changes, and switched this PR to go-namesys release, but there are some UX issues around ipfs name inspect
that should be easy to fix, and better to do it now as we may not have better oportunity later.
See comments below, I'll do another pass on this when I'm back on Thursday 🙏
204ea6f
to
8b48923
Compare
8b48923
to
1e4c6a0
Compare
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.
Thank you @hacdias!
It turns out that the option
--ttl
inipfs name publish
was never being used, and all IPNS records were being published with aTTL
of 0. This was happening because the TTL was being passed to a different package through context, but because types are different (and context is not designed for that), the value would never get tonamesys
.I updated the required packages to add the options and consolidate
Publish
andPublishWithEOL
into a single function with optional options. See linked PRs.