Fix: ignore chain in update collection method #15
Conversation
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
renanccastro
approved these changes
Dec 3, 2024
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.
Fix ESLint rule to properly handle method chains
Problem
The ESLint rule
no-sync-mongo-methods-on-serverwas incorrectly flagging method chains as errors when they weren't MongoDB-related sync operations. Specifically, it wasn't properly handling cases where the chain includedCallExpressiontypes, such as incrypto.createHmac().update().Solution
Enhanced the method chain detection to consider both
MemberExpressionandCallExpressiontypes in the object chain. This allows the rule to properly skip validation for non-MongoDB method chains while still catching actual sync MongoDB operations.Changes
CallExpressionin the chain detection logiccrypto.createHmac().update()to verify the fix