Mario, Perhaps I was a bit brief in my original post but I only want the mechanism to detect and you can leave the user to handle them, renaming them is so they can still be imported and reviewed, If I do that 4 times without review and making a decision then I deserve the confusion.
It already happens somewhat with the upgrade mechanism, rejecting shadows and core, but I want to to quarantine edited shadows to help the upgrade. Then provide a method to review and apply. Regards Tony On Wednesday, June 3, 2020 at 10:59:30 PM UTC+10, PMario wrote: > > Hi, > > What happens if you import the same stuff 4 times. Do you get 4 renamed > and duplicated tiddlers, where nobody knows, which one to use? > > I think, this is plugin territory. In TW one of several "strong" principle > says: "User content always wins" ... and I think, that shouldn't change. > > I personally wouldn't want, that the import process invalidates content > that I created. The import dialog has a possibility to view and evaluate > every single tiddler, if it should be imported or not. It's simple to see, > the "difference" between existing tiddler and the imported one. ... If > users don't do that, imo it's not the fault of the mechanism. > > There is a th-importing-tiddler hook, which can be used to create a > behaviour as you describe it, but I think this is usecase dependent and > should be implemented as a plugin first. > > -mario > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" 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/tiddlywikidev/b7252024-0b09-434f-8654-4ffc8cc80a4b%40googlegroups.com.
