Local file syncing does not respect tag condition

[Wolter HV]

I have tested the local file syncing and chose to sync only tasks with tag "Sync" or "@Sync" and I get a whole lot of tasks synced into the file.

[Izidor Matušov (izidor)]

I can reproduce it. Local file at the moment is designed to be only a default backend. We should decide if we want to support usecase with multiple local files or remove the option to add and modify it

[Wolter HV (wolterh)]

Well I think that it is a very interesting feature, specially since it
uses XML format, which could be given a style so it would be in a
readable format.
Lets say a good example of this would be to print out TODO lists.
Perhaps you don't want to know all of your pending tasks stored in your
session, but just a few - so you give these a common tag and print out
the local file, which is readily synchronized for you.

[Izidor Matušov (izidor)]

The question is if we can find a good use case for it. When would you like to have a subset of your tasks stored somewhere else than other tasks? XML is not suitable for printing. There is a plugin for that already. Any good idea for a good use case? Otherwise we should get rid of that feature.

[Wolter HV (wolterh)]

Well by definition XML is a very extensible language - many could ramble about possible uses that could be given to this feature, but perhaps it is indeed a wiser idea to redirect efforts where they're needed more.

[Izidor Matušov (izidor)]

I'm looking for a use case where you take the output XML and put it into another program to get something. If you need to write a piece of XSLT or maybe program a script, you can do it directly from main tasks.

[Alan Gomes Alvino (alangalvino)]

Hi, i'll try provide a implemantation.

[Izidor Matušov (izidor)]

Have a look at GTG/core/datastore.py method should_task_id_be_stored(). You should create a liblarch tree with a filter for each backend. Also look in get_task_filter_for_backend()