Closed ggalmazor closed 4 years ago
I think it doesn't make sense to block the release for more time. If the feedback comes and we can repro the original issue, we will release v1.17.1 with the fix.
Hi @ggalmazor Sorry have been super busy and not managed to keep up with you on this. I guess as this flagged up an issue with preferences, it is possible that the fix you've made will change the behaviour I was seeing, so suggest we wait until next release and check to see if this fixes it. Thanks so much.
No problem @chrissyhroberts! Thank you for understanding :)
Closes #812
In this PR
What has been done to verify that this works as intended?
Testing of this PR involves this steps:
-c
CLI op to clear all preferencesIn master, you are asked to set an sd for a second time, which shouldn't happen.
Why is this the best possible solution? Were any other approaches considered?
This is a super narrow fix. No other approaches were considered.
Somehow, setting the sd in the pull CLI ops was losing prefs for the GUI, and users were asked to set it again in the next GUI launch.
Also, setting the sd in CLI ops is not required (downstream code gets the briefcaseDir directly), so it's a safe change to do.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
I tried to track uses of
BriefcasePreferences.getStorageDir()
in downstream code that would require the call toBriefcasePreferences.setStorageDir()
I've removed and I found none. I could have missed something, though.Does this change require updates to documentation? If so, please file an issue at https://github.com/opendatakit/docs/issues/new and include the link below.
No.