Replies: 3 comments 2 replies
-
The import handling already has a full fetched diffing mechanism. You can diff fields or the full-text if you want to. ... Is that not enough? |
Beta Was this translation helpful? Give feedback.
-
So, here is my proposal. I wish for the import mechansim to do the following:
I can imagine that this would not be a fool proof method to find what needs attention but it is definitely a good indicator, and it would substantially simplify handling of overwrites. The import mechanism is in JS so it is beyond a regular TW user to implement this proposal. But if this is in place, it is simple enough to build further things from there, in wikitext, like alert-lists of overwrites that need attention after an update, etc. Anyone wanting to add something before I make an official request for this? |
Beta Was this translation helpful? Give feedback.
-
Posted Issue: Indicated overwrites that need attention from updates Give it a thumbs up there if you agree this would be useful. |
Beta Was this translation helpful? Give feedback.
-
"Warning, don't edit shadow tiddlers because..."
During imports or attempted upgrades we are alerted about conflicting version numbers. Presumably there's some little mechanism comparing these numbers.
For shadows, could this same mechanism (or some other for that matter) be used to compare all the fields of the updated shadow with the original shadow to inform if there is actually any difference between these? This is highly valuable info for overwritten shadow tiddlers. I'm not asking for a full text diff comparison (alto that would be nice), just an indication if the updated shadow is identical or not to the old one - (bare the date which is likely changed for the update). Often individual shadow tids are not updated in an updated plugin.
Overwrites might not be as problematic if there was an indication that "compared to the last version, this shadow tiddler has changed / not changed".
Beta Was this translation helpful? Give feedback.
All reactions