[server-preset] Implement LRU cache mapper vs types file comparison - #487
Merged
Conversation
🦋 Changeset detectedLatest commit: dd267ab The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Owner
Author
|
/release-snapsho |
Owner
Author
|
/release-snapshot |
Contributor
|
✅ Snapshot published @eddeee888/gcg-operation-location-migration@0.0.0-pr467-run390-1-20260809065829
@eddeee888/gcg-server-config@0.0.0-pr467-run390-1-20260809065829
@eddeee888/gcg-typescript-resolver-files@0.0.0-pr483-run422-1-20260827135158 |
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.
Add LRU cache for resolver types vs mappers type check
Resolver types vs mappers check is the most expensive check in this plugin. We need this to determine which resolvers need to be added to avoid runtime errors.
Previously in watch mode, we run this expensive check every run, even if the schema or mappers don't change. Adding a LRU cache helps said scenario by re-using a previously parsed data.
This ensures the codemod scenarios, where schema or mappers don't change, run as efficiently as possible: