-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Platform Docs: Fix missing link #57145
Conversation
ff17532
to
7d373e3
Compare
Size Change: 0 B Total Size: 1.71 MB ℹ️ View Unchanged
|
Flaky tests detected in 7740e98. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7246246973
|
@@ -100,7 +100,7 @@ After running this through the parser, we're left with a simple object we can ma | |||
|
|||
This has dramatic implications for how simple and performant we can make our parser. These explicit boundaries also protect damage to a single block from bleeding into other blocks or tarnishing the entire document. It also allows the system to identify unrecognized blocks before rendering them. | |||
|
|||
_N.B.:_ The defining aspects of blocks are their semantics and the isolation mechanism they provide: in other words, their identity. On the other hand, where their data is stored is a more liberal aspect. Blocks support more than just static local data (via JSON literals inside the HTML comment or within the block's HTML), and more mechanisms (_e.g._, global blocks or otherwise resorting to storage in complementary `WP_Post` objects) are expected. See [attributes](/docs/reference-guides/block-api/block-attributes.md) for details. | |||
_N.B.:_ The defining aspects of blocks are their semantics and the isolation mechanism they provide: in other words, their identity. On the other hand, where their data is stored is a more liberal aspect. Blocks support more than just static local data (via JSON literals inside the HTML comment or within the block's HTML), and more mechanisms (_e.g._, global blocks or otherwise resorting to storage in complementary `WP_Post` objects) are expected. See [attributes](https://github.com/WordPress/gutenberg/tree/HEAD/docs/reference-guides/block-api/block-attributes.md) for details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think maybe we should remove the link for now, until we have a dedicated reference for attributes (to avoid confusing them with WP jargon)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. I deleted the entire sentence including the link, is this correct?
* Platform Docs: Fix missing link * Remove link
Related #53874
What?
This PR fixes one link. This will also allow the
npm run build
command to work correctly.Why?
The
/docs/
path link will work correctly in markdown on GitHub repository. However, if this document is published in the future, the docs directory will not exist and will not be linked correctly.Testing Instructions
./platform-docs
npm install
npm run build