Todo-txt format in Api Baserow

[anon59363363]

Hi @lucw, how are you?

Before answering some of your questions, I’d like to say thank you very much for commenting here.

@lucw

Feels like a plugin could work nicely with this.

thanks for this feedback here.

@lucw

But I question how you’ll interact with the data.

Please, see this: Using the Baserow api to import tasks from a txt file(todo.txt) for more informations if possible.

@lucw

A todo list is not something static.

This is true.

@lucw

Do you upload once ?

Yes.

@lucw

What happens when you need to update, do you update in baserow ? Or do you update the todo.txt, and re-upload ?

I didn’t think about updating the file, just sending the file data in Baserow with the http-post method, and viewing the information with the http-get method.

@lucw

It’s important to think of the lifecycle of data, because that will dictate how you design the whole thing.

I would like to name “two data flows”: an ideal data flow and the data flow I created.

1. In an ideal flow of data it would be something like this:

1.1 The best way would be that every change in the txt file is saved locally in SQLite and the update is sent to Baserow with date and time.

1.2 In case I need to know which tasks were executed, I have the complete history in Baserow with date and time.

1.3 However, if I need a backup, as I have a local copy, it’s easy to go back to the old version.

---

2. The data flow I developed is very different from this ideal flow:

2.1 I thought that for most developers having “VSCode” is something very easy to install.

2.2 Then, in general, you install VSCode with an extension called “local-history” that generates an automatic copy of the files you modify in VSCode.

2.3 Then, I installed python to run this algorithm which loads the todo.txt file only once in Baserow.

---

Which of these data streams is the best: 1 or 2? Is this thought interesting? What do you think of these ideas?