need of re-initialization after each change #13

Activity

1. ilgooz

   added

   question

   on Jul 12, 2020
2. ilgooz

   assigned

   fadeev

   on Jul 12, 2020
3. ilgooz

   changed the title [-]need re-initing after each change[/-] [+]need of re-initialization after each change[/+] on Jul 12, 2020
4. fadeev commented on Jul 12, 2020

   

   fadeev

   on Jul 12, 2020

   Contributor

   More actions

   We need to install dependencies only if something has changed in the imports, like with any other go program.

   Initialization is trickier. Right now we basically nuke all app data on every change, because very often any change to the source of the app makes the state stored in data directory invalid. It may be safer to recreate everything from scratch every time, because I don't think we can safely determine when it's ok to keep the old data.

   This can be mitigated by having a better init config. Perhaps, a YAML file that has sections for cleaning the old data, creating users, using mock data to populate the store.
5. sync-by-unito

   unassigned

   fadeev

   on Jul 30, 2020
6. fadeev commented on Apr 9, 2021

   

   fadeev

   on Apr 9, 2021

   Contributor

   More actions

   Old issue, no longer relevant. Oh, this is before we had config.yml. Good ol' days.
7. fadeev

   closed this as completedon Apr 9, 2021
8. ilgooz

   added a commit that references this issue on Jan 5, 2022

   feat: upgrade sdk to v0.44.0 (#13)

   10cc3b2