This repository has been archived by the owner on Jan 15, 2019. It is now read-only.
Release/v0.1.8 #1
Merged
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
added 2 commits
May 4, 2017 11:00
The big performance boost here comes from the change to isTrackingPath(). Previously, I was using an Array function with Object.keys on this.library to check for previously tracked paths. That was a huge misstep on my part as it's MUCH faster to simply use a JavaScript Object property lookup.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changelog
pruneLibrary()updateLibrary()isTrackingPath()to use JavaScript Object property lookup instead of Object.keys Array functions - major performance boostBreaking Changes
None! :)