achetverikov
commented
7 years ago I guess for now we might ignore backward compatibility, while later we might want to add some checks to ensure that changes in config don’t break older files (or just take notice of that and change older configs accordingly)
Andrey Chetverikov, Ph.D. PostDoc
Donders Institute for Brain, Cognition and Behavior Center for Cognitive Neuroimaging
Netherlands
Phone: +31 64 9095738 E-mail: andrey.a.chetverikov@gmail.com mailto:andrey.a.chetverikov@gmail.com
From: jimijimiyo [mailto:notifications@github.com] Sent: Tuesday, August 15, 2017 03:15 PM To: achetverikov/visual_search_db visual_search_db@noreply.github.com Cc: Andrey Chetverikov stop.psy@gmail.com; Mention mention@noreply.github.com Subject: [achetverikov/visual_search_db] Config files backward compatibility (#7)
For now we don't have it. Thus, with changing config file we need to change all the older config files, as required/optional fields changed. @achetverikov https://github.com/achetverikov what do you think? And should I change existing configs?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/achetverikov/visual_search_db/issues/7 , or mute the thread https://github.com/notifications/unsubscribe-auth/ABZdzkM4n7tap5F-jLc7YB__imlIxF0Vks5sYZncgaJpZM4O3kb4 . https://github.com/notifications/beacon/ABZdzuhzpNSEra78SNXK7TSEKP7ywXbdks5sYZncgaJpZM4O3kb4.gif
For now we don't have it. Thus, with changing config file we need to change all the older config files, as required/optional fields changed. @achetverikov what do you think? And should I change existing configs?