Is your feature request related to a problem? Please describe.
First of all, thank you for building and maintaining confluence-cli — it's become a regular part of my workflow and I really appreciate the work you've put into it. 🙏
I wanted to flag one small friction point in case it's useful. When Confluence's "Copy link" button gives me a tiny link like https://example.atlassian.net/wiki/x/aBcDeFg and I try to pass it to a command, it isn't recognised as a <pageId>, even though numeric IDs, pageId= URLs, pretty /pages/<id>/ URLs, and /display/ URLs all work. I end up having to look up the numeric ID by hand.
Describe the solution you'd like
It would be lovely if extractPageId could accept tiny links directly, so that confluence read, confluence attachments, etc. just work with whatever URL the user copied from the browser — no pre-processing needed.
Describe alternatives you've considered
Resolving the tiny link in shell before passing it in works as a workaround, but it's an extra step every time and I suspect most users will hit it before they know to avoid it.
Use case
Anyone who copies a link out of the Confluence UI (the default "Share" action produces a tiny link rather than a numeric ID or pretty URL) and pastes it straight into a CLI command. It would also make life easier for scripts and agents that receive Confluence URLs from users without being able to assume which URL format they'll get.
Additional context
I don't have a strong opinion on how this should be implemented — I'm happy to leave that to your judgement, since you have much better context on the codebase's conventions and trade-offs than I do. Please feel free to close this if it doesn't fit the direction you have in mind for the project, or if it's lower priority than other work.
Thanks again for considering it!
Implementation suggestions
(Intentionally left blank — deferring to the maintainer's preferred approach.)
Is your feature request related to a problem? Please describe.
First of all, thank you for building and maintaining
confluence-cli— it's become a regular part of my workflow and I really appreciate the work you've put into it. 🙏I wanted to flag one small friction point in case it's useful. When Confluence's "Copy link" button gives me a tiny link like
https://example.atlassian.net/wiki/x/aBcDeFgand I try to pass it to a command, it isn't recognised as a<pageId>, even though numeric IDs,pageId=URLs, pretty/pages/<id>/URLs, and/display/URLs all work. I end up having to look up the numeric ID by hand.Describe the solution you'd like
It would be lovely if
extractPageIdcould accept tiny links directly, so thatconfluence read,confluence attachments, etc. just work with whatever URL the user copied from the browser — no pre-processing needed.Describe alternatives you've considered
Resolving the tiny link in shell before passing it in works as a workaround, but it's an extra step every time and I suspect most users will hit it before they know to avoid it.
Use case
Anyone who copies a link out of the Confluence UI (the default "Share" action produces a tiny link rather than a numeric ID or pretty URL) and pastes it straight into a CLI command. It would also make life easier for scripts and agents that receive Confluence URLs from users without being able to assume which URL format they'll get.
Additional context
I don't have a strong opinion on how this should be implemented — I'm happy to leave that to your judgement, since you have much better context on the codebase's conventions and trade-offs than I do. Please feel free to close this if it doesn't fit the direction you have in mind for the project, or if it's lower priority than other work.
Thanks again for considering it!
Implementation suggestions
(Intentionally left blank — deferring to the maintainer's preferred approach.)