The current configuration caching uses the version string to check for equivalence. This does not work if multiple files have the same version (eg) using date for version number and uploading multiple on the same day.
It is obvious that relying on the user to generate unique non-colliding version numbers is unreasonable.
Also it looks like things are getting stored in local storage instead of session storage as the naming of variable suggests.
The current configuration caching uses the version string to check for equivalence. This does not work if multiple files have the same version (eg) using date for version number and uploading multiple on the same day.
It is obvious that relying on the user to generate unique non-colliding version numbers is unreasonable.
Also it looks like things are getting stored in local storage instead of session storage as the naming of variable suggests.