20 const data = payload?.data;
21 const pageId = data?.id;
22 const databaseId = data?.parent?.database_id;
23
24 // this endpoint is for a specific database page and is triggered by a button in that database page
25
26 // the button that calls this endpoint sends a payload with the id of the database page, and the id of the parent database
27 // (e.g., pageId and databaseId from the payload)
28
29 // different than other endpoints, this one does not get called by a reset button or the cron reset
30 // instead, the reset button and the reset cron target the database, not the page
31 // so, we don't have a reset call coming in with the x-blob-key custom header to this enpoint
32 // nor do we have a x-container-title header that holds the title of the target object coming from the button payload
33
34 // both the reset button and the reset cron delete all database pages, and then add back fresh pages
35 // the endpoint for that is /example-database-pages (note the "s" at the end)
36
37 // different than other endpoints, we get the id of the block to modify (ie, the database page) from the button payload
38 // so, we don't need to do the things we do at other endpoints to get the id of target block
39 // (e.g., search the blob cache, or traverse notion page objects)
40
41 // but, we do need to set the blob for the resets
42 // and for that we'll need the id of the page in which this database lives
43 // and an identifier for the database
44
45 // can that idenfifier be the databaseId rather than the database title?
46 // the reset button sends the database title to the .../pages endpoint in order to find the id of the database
47 // but the matching there will traverse the notion page database objects looking for a title match
48 // which has nothing to do with the database title in the blob
49
50 // note: if you're wondering why none of the notion buttons have hard-coded ids for the targeting
53 // as is, i can clone a page with examples for a guest and everything will work without anyone needing to edit button settings
54
55 // when a user adds a favicon to a database page, we need to capture in the blob cache that a page in this database has been updated
56 // so that resets know which database to reset
57 // but the payload of the favicon button in this page does _not_ send the id of the page in which the database lives
58 // nor does it send the database title
59 // so we'll need to get those to make the blob key
60
67 for (const item of items) {
68 const blobData = await blob.getJSON(item.key);
69 if (blobData?.id === databaseId) {
70 // console.log(item.key, blobData);
71 blobData.key = item.key;
82
83 // blob for cache
84 // get the parent page id of this child_database
85 // this is the user's page and we need it for the blob key
86 const parentPageId = blobject?.user
87 ? blobject?.user?.page_id
88 : await notionHelpers.getDatabaseParentPageId(databaseId);
89
90 // we also need the database title
91 // even though we have the database id and it's tempting to use it here
92 // we need the title in the blob key so that the reset button can work
93 // b/c the reset button can only send the title in the x-container-title header
94 // with no other way to tie the button to the database
95
96 // const databaseTitle = blobject?.key
97 // ? (blobject?.key).split("--").pop()
98 // : await notionHelpers.getDatabaseTitle(databaseId);
99 const databaseTitle = await notionHelpers.getDatabaseTitle(databaseId);
100
101 console.log("databaseTitle:", databaseTitle);
102
103 // store webhook data in blob storage for resets
105 "slug": slug,
106 "clientPageId": parentPageId,
107 // "containerId": databaseId, // slugify databaseTitle here?
108 "containerId": await helpers.slugify(databaseTitle),
109 });
110 await blob.setJSON(blobKey, {
113 page_id: parentPageId,
114 },
115 id: databaseId,
116 date: new Date(),
117 content: askingFor,