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
We'll need to come up with an easy way of creating links between arbitrary document nodes. This serves several purposes: In the case of chained build steps, we should be able to indicate that several nodes refer to the same source.
And in the actual documentation, we need to link pages and sections too.
Due to nodes implementing ID properties already, one possible way to accomplish this would be to statically link to that. IDs are supposed to change if moved between parent nodes or another node is prepended before them.
So another possibility would be to create links using references to other nodes. This has the huge advantage of uniqueness, since the reference always points to the correct node. I'm not sure on how to implement this in a clean and solid way though, this will need a lot of whiteboard work 😄
The text was updated successfully, but these errors were encountered:
As of c11dbba, links have a somewhat stable API to build the concept on. Nodes have UIDs now, so that makes cross-tree links trivial. Links can also directly point to nodes, which is the recommended way to create links (if UIDs are passed, the setter queries the root node to find the UID so that is bad performance wise).
I'm still unsure on how this will eventually carry out for module authors, since the document API lacks many convenience methods currently. We'll see how things play out once I've got time for the actual transformer implementation.
We'll need to come up with an easy way of creating links between arbitrary document nodes. This serves several purposes: In the case of chained build steps, we should be able to indicate that several nodes refer to the same source.
And in the actual documentation, we need to link pages and sections too.
Due to nodes implementing ID properties already, one possible way to accomplish this would be to statically link to that. IDs are supposed to change if moved between parent nodes or another node is prepended before them.
So another possibility would be to create links using references to other nodes. This has the huge advantage of uniqueness, since the reference always points to the correct node. I'm not sure on how to implement this in a clean and solid way though, this will need a lot of whiteboard work 😄
The text was updated successfully, but these errors were encountered: