If you open an older version of Brackets, it resets some of your preferences

[peterflynn]

1. Launch a tip-of-tree build of Brackets and make note of what's in the Recent Projects dropdown
2. Quit that version, and launch an earlier sprint build (I used Sprint 20)
3. Note that Recent Projects dropdown is blank. (This seems like an expected, though unfortunate, side effect of the preferences id migration).
4. Open some project other than the default Getting Started
5. Quit the older version, and re-launch the latest build

Result: Recent Projects dropdown contains the project you opened in step 4, the default Getting Started, and nothing else

Expected: Preferences from latest version are unharmed

This seems like a bit of an edge case, since it's unlikely to be running old builds after upgrading (except perhaps for Edge Code, but that uses a separate prefs store). However, it's still a little worrisome... might be worth pondering for a min before this sprint closes down.

[redmunds]

@TomMalbran This is the Recent Project list problem I mentioned in this pull request (#3101) but did not have a reproducible recipe. Please take a look if you have some time.

[TomMalbran]

I'll look into it.

It would be possible to delete the old preferences only once, on the first upgrade, but leave them on the second time it tries to move the preferences. Shouldn't be that bad, since mostly only developers keep switching between older and new versions and not many users do. Although this is a problem only if you go to Brackets versions older than 22, so on the next sprint switching between the current version and the GitHub one, won't be a problem.

[TomMalbran]

I was able to reproduce this issue once following the same steps, but not again after that time.

Could it be that the preference ID changed for the recent projects in my last Preferences ID request?

[pthiess]

@redmunds Please add this to the Sprint 22 release notes and remove the flag but keep the bug open.

[peterflynn]

Removing Sprint 22 milestone per above note. Issue is already mentioned in release notes.

[pthiess]

@peterflynn I removed the release notes per your note above.

[redmunds]

This was added to Release Notes. Closing.