For Bob I made two methods for testing if a tiddler has been updated to prevent infinite update loops when syncing. One test each field of the existing and new tiddler to determine if it should be updated and the other normalises a tiddler then uses quick hashing function and compares the hashes. I didn't think there was a general use for it in the core but if it would be useful I can make a pull request with one or both. I think that the hashing method is a better option, The benefit of the other one is that you could have a list of fields to ignore when determining if a tiddler has been updated.
And now that I typed that I realised that you could just pass that to the normalisation function and it could do the same thing. Anyway, if this would be useful let me know. It has been tested in Bob for a few months now so I think all the big bugs have been caught. On Saturday, April 6, 2019 at 1:32:36 PM UTC+2, talha131 wrote: > > I have a TW running on nodejs and stored in Git. Each tiddler is a > separate file. > > When I have to sync another copy of the same TW, I drop the TW.html file > on it. TW is smart enough to create the new tiddlers. > > The tiddlers that are already present and have not changed, their modified > date is updated. > > How do I tell TW that if a tiddler is already present and its content has > not changed then do not touch its modified date? > > Or how to tell TW, when importing another wiki, do not copy the modified > date? > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b79874c2-758e-4dc3-88d0-f20cdc0a2187%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
