Hi there,
First of all, thank you for your amazing work on this package – it’s been extremely useful!
Let me give you a bit of context: I’m using this library to build a tool that synchronizes local Markdown documents with Confluence. Based on the file structure, it recreates the hierarchy as Confluence pages.
However, I’ve encountered an issue when a page has more than 25 children. The Confluence API only returns the first 25 by default, so my sync logic doesn’t find the remaining children and tries to create them again, which causes errors because those pages already exist.
It would be really helpful if the contentChildrenAndDescendants.getContentChildren method accepted start and limit parameters, so we could implement proper pagination and fetch all children recursively.
Would you be open to adding support for this, or would you accept a PR for it?
Thanks again for your work!
Hi there,
First of all, thank you for your amazing work on this package – it’s been extremely useful!
Let me give you a bit of context: I’m using this library to build a tool that synchronizes local Markdown documents with Confluence. Based on the file structure, it recreates the hierarchy as Confluence pages.
However, I’ve encountered an issue when a page has more than 25 children. The Confluence API only returns the first 25 by default, so my sync logic doesn’t find the remaining children and tries to create them again, which causes errors because those pages already exist.
It would be really helpful if the contentChildrenAndDescendants.getContentChildren method accepted
startandlimitparameters, so we could implement proper pagination and fetch all children recursively.Would you be open to adding support for this, or would you accept a PR for it?
Thanks again for your work!