Skip to content

Conversation

@pandeymangg
Copy link
Contributor

@pandeymangg pandeymangg commented Jul 7, 2025

Fixes #12

Adds a filter in the filterSurveys function that filters out surveys having segment filters if userId is not set (Anonymous usage). Also adds a test for this

How to test?

  1. Add some filters in a segment in a survey
  2. Track the action which is supposed to show the survey, make sure that a userId isn't set
  3. The survey will not be triggered

Summary by CodeRabbit

  • Bug Fixes

    • Surveys with segment filters are now correctly excluded when no user ID is present.
  • Tests

    • Added a test to verify that surveys with segment filters are filtered out if the user does not have a user ID.

@coderabbitai
Copy link

coderabbitai bot commented Jul 7, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The filterSurveys function in the React Native SDK was updated to exclude surveys with segment filters when no userId is present. A corresponding test was added to verify that surveys with segment filters are not shown to unidentified users.

Changes

Files/Paths Change Summary
.../src/lib/common/utils.ts Updated filterSurveys to exclude surveys with segment filters when userId is falsy.
.../src/lib/common/tests/utils.test.ts Added a test case to check that surveys with segment filters are excluded for users without userId.

Assessment against linked issues

Objective (Issue #) Addressed Explanation
Exclude targeted surveys (with segment filters) from unidentified users (#12)
Ensure parity with JS SDK behavior for survey filtering (#12)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes were found.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@pandeymangg
Copy link
Contributor Author

@coderabbitai review

@coderabbitai
Copy link

coderabbitai bot commented Jul 7, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
packages/react-native/src/lib/common/utils.ts (1)

116-117: Consider adding a descriptive comment for the segmentFiltersLength logic.

While the logic is correct, adding a brief comment explaining why we check for filter length would improve code readability.

+ // Check if survey has targeting filters - anonymous users can't be segmented
  const segmentFiltersLength = survey.segment?.filters?.length ?? 0;
  return segmentFiltersLength === 0;
packages/react-native/src/lib/common/tests/utils.test.ts (1)

161-175: Consider adding a complementary test case for surveys without segment filters.

While the current test verifies that surveys with filters are excluded for anonymous users, consider adding a test that confirms surveys without segment filters are still included for anonymous users to ensure complete coverage.

+ test("includes surveys without segment filters for anonymous users", () => {
+   environment.data.surveys = [
+     {
+       ...baseSurvey,
+       id: mockSurveyId1,
+       segment: undefined, // No segment at all
+     } as TSurvey,
+     {
+       ...baseSurvey,
+       id: mockSurveyId2,
+       segment: { id: mockSegmentId1 }, // Segment but no filters
+     } as TSurvey,
+   ];
+
+   const result = filterSurveys(environment, user);
+   expect(result).toHaveLength(2);
+ });
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f8d2212 and d536561.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • packages/react-native/src/lib/common/tests/utils.test.ts (1 hunks)
  • packages/react-native/src/lib/common/utils.ts (1 hunks)
🔇 Additional comments (2)
packages/react-native/src/lib/common/utils.ts (1)

113-119: LGTM! Clean implementation of anonymous user filtering.

The implementation correctly filters out surveys with segment filters when no userId is present. The use of optional chaining and nullish coalescing properly handles potential undefined/null values in the segment structure.

packages/react-native/src/lib/common/tests/utils.test.ts (1)

161-175: Excellent test coverage for the new anonymous user filtering behavior.

The test case properly validates that surveys with segment filters are excluded when no userId is present. The test setup is realistic and follows the existing testing patterns in the file.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 7, 2025

@pandeymangg pandeymangg changed the base branch from release/v2.2.0 to main July 7, 2025 08:27
Copy link
Member

@Dhruwang Dhruwang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Dhruwang Dhruwang added this pull request to the merge queue Jul 8, 2025
Merged via the queue into main with commit 0c2b411 Jul 8, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Targeted surveys are shown to unidentified users

2 participants