Jeremy, thank you very much for the pointers!
While I can perfectly understand the current architecture to chose the deserializer based on the extension of the incoming file, this quickly hits a dead end when it comes to generic file formats, such as XML/.xml, without a cleary differentiating file extension. Of course, a quick workaround would be to rename the import file. But the next time I or someone else importing an updated XML file version ... so what file extension do I need to use? Also, over time I suspect that we may see more .xml files with different XML schemas. Do you see a way to allow multiple XML deserializers, based on the root element -- or maybe just based on the beginning of the XML file to be imported? Kind of a mime-type detection, just on a XML file signature? Best regards, TheDiveO -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/826cc552-f162-44ec-91c7-ebbcfc2d1542%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
