Currently, when a StorageAccessor or one of the classes it uses encounters an error, it is either silently ignored or reported as a RuntimeException that is likely to cause the application to terminate.
To allow a better user experience when errors occur, it would be good to do the following:
Create a checked exception type (or maybe a hierarchy) used to report storage errors
Make all public StorageAccessor methods that may fail throw the exception
Modify the storage code to detect problems and throw suitable exceptions
The beta release is too soon to have time to implement this, so it can be done for the feature-complete release.
Currently, when a StorageAccessor or one of the classes it uses encounters an error, it is either silently ignored or reported as a RuntimeException that is likely to cause the application to terminate.
To allow a better user experience when errors occur, it would be good to do the following:
The beta release is too soon to have time to implement this, so it can be done for the feature-complete release.