You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The page with the duplicate canonical page id won't be built. I can understand the rationale behind it, but the warning doesn't stand out very much when you've already console.log several other values during the build process. It's quite possible that the user may miss out on this warning.
There is nothing in Notion that helps user check for duplicate property values that I'm aware of. As the number of pages increase, the probability of duplicate name becomes higher. Should this kit be more stringent about duplicate page names? Like throw an error and quit the build.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
First, thank you very much for building such an awesome, well-thought-out tool. I have a question regarding the generation of canonical page ids.
When it encounters a page whose canonical page id has already been in the map, it will simply issue a warning, for example:
The page with the duplicate canonical page id won't be built. I can understand the rationale behind it, but the warning doesn't stand out very much when you've already
console.log
several other values during the build process. It's quite possible that the user may miss out on this warning.There is nothing in Notion that helps user check for duplicate property values that I'm aware of. As the number of pages increase, the probability of duplicate name becomes higher. Should this kit be more stringent about duplicate page names? Like throw an error and quit the build.
Beta Was this translation helpful? Give feedback.
All reactions