Export/Import function

[SamTada]

Any way to add a Export/Import function in Settings to backup your recipes and ingredients to a file, should you need to reinstall the app?

[anton-gustafsson]

There is currently no way to export/import any data in the app. But it is a great feature that I will add in the future. Thanks

[sbennett18]

Not totally sure how it might be helpful or not, but there's this. Could be cool to export to this format.
https://cooklang.org/

[anton-gustafsson]

@sbennett18 Cool! Thank you for the link

[ororktn]

The model of cooklang is very much different from the one used by Drinkable. As of today, I see different ways to solve the current issue:

1. Change the model of Drinkable to match the one of Cooklang
   • 👍 Cooklang is a great way to store recipes and would allow lot of new features in the future
   • 👍 Drinkable would match an external format and be more easily interoperable with other cooking and cocktail software
   • 👎 Would require a lot of work of redesign in the backend part of the code
2. Add a compatibility layer with cooklang
   • 👍 Drinkable would still be somewhat interoperable with some other software
   • 👍 Does not require to change all existing code of the app
   • 👎 There will be a lot of data loss and results will be clunky
3. Add a way (our own way) to serialize current model of Drinkable
   • 👍 Fast and easy to implement
   • 👎 Will be a custom made format, compatible with nothing else

Any opinion on this? I can take a look at option 1 that look the best to me (I'm really looking forward for features that can be enabled with cooklang), but it will require quite a bit of work that I probably won't be able to do alone.

[anton-gustafsson]

@Lugrim Thank you for sharing all of the ideas above 👍🏼

I would love to use a more used external format for storing the recipes. As you pointed out It will improve the experience for Drinkable and also maybe other apps.

I do however see an issue with converting to cooklang as it only supports english as of now. As you can read in this proposal

Could you please describe the features that cooklang would enable? Maybe we can implement them anyways?

[ororktn]

Three examples that come to my mind are:

• Having directly the quantities in the recipe (in case an ingredient appears twice) while still being able to generate an ingredient list
• Timers in recipe, could be started with a single tap on text
• Metadata (source, special warnings, ...)

Sadly, the proposal you linked looks pretty dead, I'm gonna try to bump it a bit

[BradNut]

This would also be nice to have. Just wondering if there's been any progress on this? 🙂

[ororktn]

This would also be nice to have. Just wondering if there's been any progress on this? 🙂

I guess we are waiting for updates on cooklang/spec#86 ? It would be great to switch on a cooklang model IMO, but yet, we'd have localization problems

[anton-gustafsson]

I guess we could do export /import functionality with a simple JSON file. I'm not really sure where the user would like to store it though.

[C0smin]

Would be great to be able to export/import in the current format also, is there any workaround for that?

[anton-gustafsson]

It would be great! I could implement it. Do you have any idea for where to store the data? @C0smin

[C0smin]

Hey @anton-gustafsson, I don't have great technical knowledge on how that would be implemented here, but in my mind there would be no other storage location. When user wants to export a backup, create a json and ask the user where to store it (presumably defaults to downloads). Import would be the reverse action.
I would also presume that this would backup my "My Bar" and when importing maybe the question would be what to do with the imported data, overwrite if it exists or update it (update being the more technically complicated aspect), but I would suggest this is a later expansion on the feature rather than making this one too big. Hope I make sense 😅