Memoize the findFileInCurrentPath method with fileName being the key#33
Merged
patrickocoffeyo merged 11 commits intodevelopfrom Nov 5, 2021
Merged
Memoize the findFileInCurrentPath method with fileName being the key#33patrickocoffeyo merged 11 commits intodevelopfrom
patrickocoffeyo merged 11 commits intodevelopfrom
Conversation
Contributor
Author
|
Contributor
Author
|
@patrickocoffeyo Thank you again for mentoring on this one. Sending it your way for contrib credit. |
patrickocoffeyo
approved these changes
Nov 5, 2021
Collaborator
patrickocoffeyo
left a comment
There was a problem hiding this comment.
Nice work! Thank you for putting this together 🙌
|
🎉 This PR is included in version 1.4.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or 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
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.
Summary
findFileInCurrentPathmethod withfileNamebeing the key.This PR addresses the following issue
Documentation Update (required)
Testing:
npm run testand verify it passes