After discussion with @bcdonovan I think these hard-coded version in the library managers need to be rolled as we upgrade. Case example where it breaks:
Start with fresh repo.
Create an X6 using GUI. The instrument library version will be 0.
Exit and relaunch the GUI. The migrator will fail on this line.
Our migrators are stateful and expect things to as they were in the previous version. We could try and make the migrators more robust but I think the rolling the version number is the right thing to do.
After discussion with @bcdonovan I think these hard-coded version in the library managers need to be rolled as we upgrade. Case example where it breaks:
0
.Our migrators are stateful and expect things to as they were in the previous version. We could try and make the migrators more robust but I think the rolling the version number is the right thing to do.