@Flibbles I just created a solution that uses tiddler titles as a key to a data tiddler. I believe this is not yet a feature supported by relink. Perhaps you could look into it if you can find some time?
However, I did not expect you to solve this with relink, and I did my own research into the rename mechanism, however I see relink overwrites a core tiddler to achieve this. As may my own solution to address my current case. This then becomes an issue, two solutions changing the same core tiddler.
I think there is an argument here to modify the core to allow relink, and my own solution, to be integrated without modifying a core tiddler, To me giving a designer of a wiki a way to make use of the rename event is a missing feature. Especially important in a bigger picture solution I am developing hinted at in No touch tags - or flags on tiddlers without editing or changing the tiddler - #102 by TW_Tones this solution will make use of your wonderful relink but stands to demand even more from tiddlywiki and relink than currently supported.
Perhaps you could look at your modifications in $:/core/ui/EditTemplate/title and together we can submit a suggestion to add hackability to the rename mechanism permitting relink, without modifying any core tiddler, and as a result provide a hook for other solutions that want to maintain “referential integrity”.
- The rename event can happen by a number of means and the relink message sits behind a number of tiddler messages.
@pmario I mention you here as you pointed out pending changes in the core that are related to relinking perhaps you can help with this small endeavour to add hackability on rename?
- A simple example may be on rename retrieving actions from tiddlers with a new system tag $:/tags/actions-on-rename this may include relinks hook as well thus raising with @Flibbles
- I am yet to conceptualise how relink would transition to a no core tiddler overwrite solution, while maintaining backwards compatibility.