-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2.0.0 #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Owner
jmdobry
commented
Sep 21, 2013
- - Add option specifying how frequently to check if items have expired (performance) #28 - Add option specifying how frequently to check if items have expired (performance)
- - Third option to aggressive and passive delete. #30 - Third option to aggressive and passive delete.
- - Best Practices #42 - Namespace the module
- - Refactor AngularCacheFactory#info() to return info like AngularCache#info() #45 - Refactor AngularCacheFactory#info() to return info like AngularCache#info()
- - Refactor the way a cache's options are set internally to be less convoluted #46 - Refactor the way a cache's options are set internally to be less convoluted
- - Feature delete on expire #47 - Feature delete on expire
- - cacheFlushInterval doesn't clear web storage when storageMode is used. #52 - cacheFlushInterval doesn't clear web storage when storageMode is used.
- - AngularCache#info(key) should return 'undefined' if the key isn't in the cache #53 - AngularCache#info(key) should return 'undefined' if the key isn't in the cache
- - 1.2.1 (2.0.0 bug fixes) #54 - 1.2.1 (2.0.0 bug fixes)
- - Add ability to set global cache defaults in $angularCacheFactoryProvider #55 - Add ability to set global cache defaults in $angularCacheFactoryProvider
- - Re-write README documentation to be clearer and more organized. #56 - Re-write README documentation to be clearer and more organized.
- - Feature heap delete #57 - feature-heap-delete
- - Re-write all unit tests. #58 - Re-write all units tests
- - README has incorrect examples of time spans #59 - README has incorrect examples of time spans
Conflicts: coverage/index.html coverage/src/angular-cache.js.html coverage/src/index.html docs/$AngularCacheFactoryProvider.html docs/AngularCache.html docs/AngularCacheFactory.html docs/angular-cache-2.0.0-SNAPSHOT.js.html docs/index.html docs/module-angular-cache.html package.json
Conflicts: src/angular-cache.js
ghost
assigned jmdobry
Sep 21, 2013
Conflicts: README.md bower.json coverage/index.html coverage/src/angular-cache.js.html coverage/src/index.html dist/angular-cache-1.2.0-SNAPSHOT.js dist/angular-cache-1.2.0-SNAPSHOT.min.js dist/angular-cache-1.2.0.js dist/angular-cache-1.2.0.min.js dist/angular-cache-2.0.0-SNAPSHOT.js dist/angular-cache-2.0.0-SNAPSHOT.min.js docs/$AngularCacheFactoryProvider.html docs/AngularCache.html docs/AngularCacheFactory.html docs/angular-cache-1.2.0-SNAPSHOT.js.html docs/angular-cache-1.2.0.js.html docs/angular-cache-2.0.0-SNAPSHOT.js.html docs/index.html docs/module-angular-cache.html package.json
Conflicts: docs/$AngularCacheFactoryProvider.html docs/AngularCache.html docs/AngularCacheFactory.html docs/angular-cache-2.0.0-SNAPSHOT.js.html docs/index.html docs/module-angular-cache.html
Feature delete on expire
…g lots of insiginificant changes to "docs/" and "coverage/". The "release" task will only be used on the "master" branch. The development branches will be free of having to deal with the "dist/", "docs/" and "coverage/" folders.
…nvoluted. Added increases validation for setting a cache's options. Improved the section in the README describing the configuration options. #46
Swapped `localStorageImpl` and `sessionStorageImpl` options for just `storageImpl` option.
Feature heap delete
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.