Upgrade all libraries file format during background scan #1187
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.
So far, libraries and their contained elements were not upgraded to the latest file format unless the user opened and saved them manually. Basically this works fine, but for long term it means there are lots of outdated files in the workspace which requires us to keep backwards compatibility forever. In addition , the background scan takes ages longer because it temporarily upgrades each element in memory before it can be added to the cache database.
To avoid these two problems, the background library scan now automatically upgrades any outdated library element in the workspace to the latest file format. This takes long on the first scan, but any further scan in massively faster then. In addition, it ensures that all files in the workspace are stored in the latest file format.