update inclusions when renaming
open, high, easy, Lewis Hoffman add/edit
Issue
update these much in the same way as links -- again with the rename confirmation.
Tags:
Created foo+bar, renamed it to foo+spam, but this remained the same:
Add foo+bar
I think the correct behavior for the weird example would be to ask if you want relative inclusions moved (in this case from test card foo to test card bar). Second best would be to change the {+John Abbe} to {test car bar+John Abbe}. Third best would be to not touch the inclusion syntax, but render test card foo+John Abbe as a card that doesn't exist (since it doesn't).
Here's the example john is talking about above:
Subtle rename error on relative inclusions. test card foo and test card bar exist. I created test card foo+John Abbe and relative-included it on test card foo. Then i renamed it to test card bar+John Abbe. Wagn still shows the inclusion syntax {+John Abbe} on test card foo, but renders it as test card bar+John Abbe.
Add +John Abbe
I moved it out of example because it's a renaming / caching bug that's really outside of the core issue here. if it's not ticketed already it will be soon.
--Ethan McCutchen.....Wed Jul 16 11:10:49 -0700 2008
Something has changed so that the third best option is what is happening now.
--John Abbe.....Wed Jul 23 00:21:13 -0700 2008
this was probably fixed by the 'expire old name from cache when renaming' fix. BUT it made me wonder if cascaded renames are handles properly-- looking into that.
--Lewis Hoffman.....Thu Jul 24 17:32:58 -0700 2008
