yaacovcr / angular-stored-object

Local resource support for Angular using HTML5 storage

student, programmer, radiologist, father

open-source GraphQL development sponsored primarily by ✨ the Guild ✨

• currently working 🔭 on a schema stitching executor with support for incremental delivery...
• consider 🌱 sponsoring my work...
• want to hear more? reach me at 📫 [email protected]

angular-stored-object's Issues

Feature Request: setDefaultStrategy then createOrUpdate

as discussed with Yaacov:

In theory, a combined method could be used that creates
or updates as necessary and use a default storage strategy, that is perhaps
specified when the service is created. I think this is a reasonable feature
request, especially useful when the storage strategy is not likely to
change.

_setup and __loadIntoMemory are inconsistent

in _loadIntoMemory method, we have
_storageType = (_storageStrategy === 'localStrategy') ? 'localStorage' : 'sessionStorage';
while in _setup we have
_storageType = (storageStrategy === 'localStorage') ? 'localStorage' : 'sessionStorage';

I think this 'localStrategy' in loadIntoMemory is messing with things, and so it results after a reload in having in sessionStorage things meant to be in localStorage

get from local storage at application start

Hello,

This project is very promising, but I think it miss one main use case of local storage : to be able to get back information from previous session when starting the application.

$create should not check the key is not yet used, and instanciate the value with what is found in the local storage, when the strategy used is localStorage

Or at least there should be a $get(strategey) method doing something similar.