[MGNLHOOK-331] Add children paths when `recursive` is true Created: 24/Jan/23 Updated: 23/Oct/23 |
|
| Status: | Backlog |
| Project: | Magnolia Webhooks |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Bartosz Staryga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | |
| Date of First Response: | |
| Epic Link: | Webhooks Maintenance (Phase 2) |
| Description |
|
Case Workaround Solution e.g Future |
| Comments |
| Comment by Christopher Zimmermann [ 24/Jan/23 ] |
|
bstaryga Thanks for the suggestion. I'm wondering if webhook should be responsible for sending list of all children. I guess the next app could do that without too much trouble with a rest call to the magnolia instance, right? Do you think there could be an issue with length of querystring? What if its 100 children? Or 2000? Have you seen this feature of sending list of items on webhooks feature of other CMS? |
| Comment by Bartosz Staryga [ 24/Jan/23 ] |
|
I like the idea that the webhook tells you that it has published a whole tree somehow. guess the next app could do that without too much trouble with a rest call to the magnolia instance, right?
I'm aiming here to make the life of devs easier Also, the webhook will know exactly which subpages were published, as Magnolia knows if the page was modified. It can send only the published subnodes, not all. In case we have 100 subnodes, we could avoid rebuilding all of them. Do you think there could be an issue with length of querystring? What if its 100 children? Or 2000? Have you seen this feature of sending lists of items on the webhooks feature of other CMS? |
| Comment by Marcin Milas [ 02/Feb/23 ] |
|
We're building a POC for our client with Magnolia Headless and NextJS with Revalidation on demand after publishing a page. We have about 200-300 pages with many branches. We'll try the way with another rest call to magnolia to get the subnodes and see how it works, although it looks like it would be much easier if the weebhook provided the subnodes. |