INT-1393 migrate userdata #370
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
1.2.0
to rename the user data directory frommongodb-compass
toMongoDB Compass
1.2.0
to convert preferences and user data from IndexedDB to a JSON file-based backendWhat's going on here?
The main process cannot access the data stored in IndexedDB (without spawning an electron window, which we'd like to avoid here). Since 1. happens before 3. the main process migration in this version cannot detect the last known version (which is part of the user preferences). Therefore, it will assume
0.0.0
since no JSON-stored data is present, which will trigger the newly added migration point at1.2.0
. However, future versions will be able to read the preference data and detect the last known version even in the main process.Testing and Verification
To test, I recommend the following steps:
~/Library/Application Support/
mongodb-compass
npm start
)MongoDB Compass
directory is createdmongodb-compass
directory disappears (because it is copied toMongoDB Compass
)This change is