BUG: When I download my document from google docs all my YAML header is missing! about trackdown

[ClaudioZandonella]

Hi @dfranquesa,

Thanks for reporting this problem.

Sorry, I don't see the zip folder could you please send it again?

In this case, it would be important to have a copy of the version of the document from google docs as well. Could you please copy and paste it from google docs into a .txt file? Probably the first few lines (15~20) should be enough to understand the problem.

Thanks!

[dfranquesa]

No, thank you for your contribution!
Now I've attached the zip file with a copy of the doc file.
My five cents are: If it's possible before replacing the local Rmd file you should make a backup of it (file_to_replace-bak.Rmd). This way if something went wrong you will always have the backup file. :-)
Thanks!
David
bug_trackdown_.zip

[ClaudioZandonella]

Thanks @dfranquesa,

I see that the problem is the same as for issue #17. For unknown reasons the [[document-header]] tag is missing and 1 is placed instead. This is really strange also because when downloading, instead of restoring the header code, again another 1 is placed.

Unfortunately, I can not reproduce this error on my computer. Could you please help us to understand the reason behind this error? I close this issue and I will give you more information directly in issue #17. Thanks!

Regarding the backup feature, you are right! A backup is really useful if something goes wrong. However, I would strongly suggest using git to track files changes. I think there is no better solution than git. My typical workflow is to commit the file before uploading it to google drive (sometimes it could be also useful to do it in a new branch) then when I download the file from google drive I check if everything is ok and, if something went wrong, I can easily go back to the previous version of the file using the RStudio git pannel. I know this part of the workflow is not well documented. Unfortunately, the actual workflow depends mostly on personal preferences. But we will definitely add more about how to integrate git in the trackdown workflow.

[ClaudioZandonella]

Closing issue as the problem is the same of issue #17. Refer to issue #17