Due to receiving more reports about the collection log not correctly loading and users having to manually click through each collection log to update I investigated what the newly introduced bug was.
After my last PR #33 I removed the old format loading, but was a bit too ignorant for regressing testing it. The new saves were not loaded, as only the /data/ directory would be iterated and the loadCollectionLogFiles function would check if the directory contains files. As the /data/ directory only contains directories of the user accounts, it would return, practically doing nothing.
Reworked the loadCollectionLogFiles function to invoke the loadCollectionLogFiles overload for each user account directory.
Due to receiving more reports about the collection log not correctly loading and users having to manually click through each collection log to update I investigated what the newly introduced bug was.
After my last PR #33 I removed the old format loading, but was a bit too ignorant for regressing testing it. The new saves were not loaded, as only the
/data/directory would be iterated and theloadCollectionLogFilesfunction would check if the directory contains files. As the/data/directory only contains directories of the user accounts, it would return, practically doing nothing.Reworked the
loadCollectionLogFilesfunction to invoke theloadCollectionLogFilesoverload for each user account directory.