-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility of loadDFG! with new module naming? #618
Comments
Do you mean you want backward compatibility? |
Yes, is that something reasonable, or just way too crazy? |
it's not super serious, but lets at least actively decide to include or exclude that kind of compatibility? I'm like 80% don't be compatible, until we learn otherwise? |
@GearsAD had some ideas of how to convert files saved in for instance v0.9 to v0.10. Can’t exactly remember the details though. |
Its been breaking with every minor so far. Thats why asked for test and versions that Sam is implementing. |
problem is too many breaking changes at once requiring blind updates to code for a few hours before I'm able to make progress again. e.g. when trying to make a new fg tar to fix serialization change, i also get a new error between yesterday and today: LoadError: no promotion exists for DateTime and TimeZones.ZonedDateTime updates to downstream code has to happen anyway, just not a smooth transition from DFG v0.9 to v0.10 unfortunately. Maybe next cycle. |
I think it was removed from deprecated too soon. Maybe just put it back. That was changes from v0.8 to v0.9 |
sounds good thanks! |
@dehann On second thought. Your data should work. If the softtype doesn’t have a module it should look in Main like before. Can you upload the file somewhere. Then I’ll check. Edit: sorry i see you do refer to file. I’ll test it. |
I had a look on my phone and the issue comes from inconsistencies in how the softtype used to be serialized. Its different in the variable and variable node data. So can do easy patch that we can remove later. The only limitation might be that it has to be the new stateless softtypes. |
i agree with your suggestion, and would add that we should permanently do automation inside |
HI @Affie , is it reasonable to require compatibility with new module names inside serialization? For example a FileDFG object that does not have any module information should be able to load like it always has?
Use this as a test: #582 (comment) which should load and give something similar to #582 (comment)
The text was updated successfully, but these errors were encountered: