My sense of the way that use_legacy_defaults should work is that if I had code that was working in some version and it stops working in a future version, I should be able to use use_legacy_defaults to return things to the version that was working.
So, for example, if I had things working in 0.8.2 and I upgrade to 0.8.4 or 0.9.0 and things stop working, I should be able to say
use_legacy_defaults('0.8.2')
and my code will work again.
This particular call definitely won't work (use_legacy_defaults only recognizes '0.8.3') and it is not clear to me how it could work. Basically, it seems like we need to track when a change in default behavior occurred and then "revert" any defaults that are different between the version I was using and the current version.
@sawyerbfuller Does my issue make sense? This is related to PR #431, I think.
My sense of the way that
use_legacy_defaultsshould work is that if I had code that was working in some version and it stops working in a future version, I should be able to useuse_legacy_defaultsto return things to the version that was working.So, for example, if I had things working in 0.8.2 and I upgrade to 0.8.4 or 0.9.0 and things stop working, I should be able to say
and my code will work again.
This particular call definitely won't work (
use_legacy_defaultsonly recognizes '0.8.3') and it is not clear to me how it could work. Basically, it seems like we need to track when a change in default behavior occurred and then "revert" any defaults that are different between the version I was using and the current version.@sawyerbfuller Does my issue make sense? This is related to PR #431, I think.