On Tuesday, April 21, 2020 at 9:56:26 AM UTC-4, Edward K. Ream wrote: > > Innovation almost happens without a juicy problem. The problem that > inspired these thoughts was this: how can we associate unit tests with (the > code in) a Leo node? > [snip] >
> Leo already has unl's (uniform node locators). There is nothing to prevent > two-way unl's between code and unit tests. Each node (containing code to be > tested) could contain a link to a tree containing zero or more unit tests. > Each unit test could optionally contain a link back to the node being > tested. So there is a (benign) many-to-one relationship between the links. > You may not remember, but I developed a script for the zettelkasten system that does something much like this. Given that you have a node that contains a line :target: followed by the gnx of the target node, the script inserts the gnx of the current node into the target node if it doesn't already have it - to serve as a backlink - and then jumps to the target node. This script could be the starting point for what you are thinking of. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/eb9c144e-cf2e-400b-86cc-5ac2bfed6c30%40googlegroups.com.
