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 PR #61198 was created (and merged) to fix this specific update but the issue with the docs generation remains
It seems the current system generates docs of the Block Editor Handbooks when two markdown files have the same name (even when they are in different paths)
This should be either fixed or a warning should be displayed when running npm run docs:build and related scripts
Looking at the git history of the manifest.json file, this has happened in the past, see #37505
IIRC, this is a limitation of the handbook setup: it creates pages for every entry present the manifest.json based on their slug, so it has to be unique. Back in the days, there was a import-block-editor.php in meta that did this job, but I can no longer find it. This ticket https://meta.trac.wordpress.org/ticket/5019 references that file.
I agree it'd be a nice improvement for the scripts to prevent you from committing if there's a repeated slug.
After merging #61143 for some reason the Quick Start Guide of the Intereactivity API meant to be at "Block Editor Handbook > Reference Guides > Interactivity API Reference > Quick Start Guide" (se toc.json) has been created at https://developer.wordpress.org/block-editor/getting-started/quick-start-guide/ (replacing the former one) and the url https://developer.wordpress.org/block-editor/reference-guides/interactivity-api/quick-start-guide/ redirects there
The PR #61198 was created (and merged) to fix this specific update but the issue with the docs generation remains
It seems the current system generates docs of the Block Editor Handbooks when two markdown files have the same name (even when they are in different paths)
This should be either fixed or a warning should be displayed when running
npm run docs:build
and related scriptscc: @ryanwelcher @ndiego @oandregal
The text was updated successfully, but these errors were encountered: