Jon Koops

I think the currently described implementation still undesirable because it exposes the implementation to the user too soon. Alternative storage solutions should be included in the library itself and they...

So to demonstrate in code: ``` js // Configuration with defaults. myModule.config(function (OAuthTokenProvider) { OAuthTokenProvider.configure({ name: 'token', storage: ['cookie', 'session', 'memory'], // Falls back to next storage method until `isSupported()`...

@joaogranado I think it's more than acceptable. The real complexity is in the cookie storage method, which requires lot's of code to parse and write cookies. For this we could...

Yes, I completely agree we should provide an easier way to extend the functionality. My proposed solution is backwards compatible as well, let there be no doubt about that. It...

I haven't received any feedback so I am assuming there isn't any interest in having the proposed method implemented. I've forked this repository for my own purposes so I can...

I agree with @joaogranado. If a solution is in sight it would be preferential to use angular-local-storage in my opinion. We could implement this without introducing breaking changes by supporting...

I'll try to help get the feature merged in angular-local-storage so we can do this asap.

Okay, angular-local-storage now has support for secure cookies! I currently don't have time to implement it, but I'll probably be able to do so in the coming weeks.

Could you provide an example schema with the expected output? There is no way to overwrite this from the generation perspective, we simply use the information provided by the schema.

Closing this. AFAIK the name is determined by the schema, so this is working as expected.