Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: hide zoho detination setting for vdmv2 #1913

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

am6010
Copy link
Contributor

@am6010 am6010 commented Feb 27, 2025

What are the changes introduced in this PR?

Write a brief explainer on your code changes.

What is the related Linear task?

Resolves INT-XXX

Please explain the objectives of your changes below

Put down any required details on the broader aspect of your changes. If there are any dependent changes, mandatorily mention them here

Any changes to existing capabilities/behaviour, mention the reason & what are the changes ?

N/A

Any new dependencies introduced with this change?

N/A

Any new checks got introduced or modified in test suites. Please explain the changes.

N/A


Developer checklist

  • My code follows the style guidelines of this project

  • No breaking changes are being introduced.

  • All related docs linked with the PR?

  • All changes manually tested?

  • Any documentation changes needed with this change?

  • I have executed schemaGenerator tests and updated schema if needed

  • Are sensitive fields marked as secret in definition config?

  • My test cases and placeholders use only masked/sample values for sensitive fields

  • Is the PR limited to 10 file changes & one task?

Reviewer checklist

  • Is the type of change in the PR title appropriate as per the changes?

  • Verified that there are no credentials or confidential data exposed with the changes.

Summary by CodeRabbit

  • New Features
    • Standardized the configuration interface by adding prerequisite controls across several settings.
    • Users will experience enhanced consistency and control in module settings, duplicate verification, trigger options, and multi-select pick list behaviors.

Copy link

coderabbitai bot commented Feb 27, 2025

Walkthrough

The pull request updates the Zoho destination configuration by adding a new "preRequisites" object to specific fields in the ui-config.json file. Each affected field now includes a feature flag with the key "AMP_vdm-next" set to false. The modifications occur in the Module Settings, Optional configuration settings, Zoho Trigger Option, and Field Level Specification sections, standardizing the prerequisites across the configuration.

Changes

File Change Summary
src/.../zoho/ui-config.json - Module Settings: Added "preRequisites" with "featureFlags": [{"configKey": "AMP_vdm-next", "value": false}] to the module field.
- Optional configuration settings: Updated addDefaultDuplicateCheck note similarly.
- Zoho Trigger Option: Modified trigger default field with the same flag.
- Field Level Specification: Updated note for Multi Select Pick List Field Action Mapping with the new prerequisites.

Suggested reviewers

  • lvrach
  • ssbeefeater
  • debanjan97
  • cisse21
  • 1abhishekpandey
  • ItsSudip
  • sandeepdsvs
  • krishna2020

Poem

I'm a little rabbit, hopping near the code,
With changes crisp and clear, lightening up the load.
New prerequisites in place, flags shining in the night,
Configurations aligned, making everything just right.
From fields to triggers, the path is set anew,
Happy hops in the dev garden, cheers from me to you!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f4485cd and 53a4cae.

📒 Files selected for processing (1)
  • src/configurations/destinations/zoho/ui-config.json (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/configurations/destinations/zoho/ui-config.json
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Analyze (java-kotlin)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate unit testing code.
    • @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.

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 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.

Copy link

codecov bot commented Feb 27, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (95870de) to head (53a4cae).

Additional details and impacted files
@@            Coverage Diff            @@
##           develop     #1913   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines           53        53           
  Branches         7         7           
=========================================
  Hits            53        53           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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 (1)
src/configurations/destinations/zoho/ui-config.json (1)

88-96: Optional Configuration Settings: Note Text Improvement.
The addition of the "preRequisites" block to the "addDefaultDuplicateCheck" field is correctly implemented. However, the note contains a redundancy ("as primary" is repeated). Consider revising it for clarity; for example, change it to:
"Rudderstack will use the identifier field as the primary duplicate check field."

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between fe22b4b and f4485cd.

📒 Files selected for processing (1)
  • src/configurations/destinations/zoho/ui-config.json (4 hunks)
🔇 Additional comments (3)
src/configurations/destinations/zoho/ui-config.json (3)

70-78: Module Settings: Valid use of preRequisites.
The added "preRequisites" block with the "featureFlags" for the "module" field is clear and consistent with gating the configuration based on feature flags. It aligns well with the PR objective by conditionally hiding settings based on the "AMP_vdm-next" flag.


130-138: Zoho Trigger Option: Consistent Feature Flag Handling.
The updated field now explicitly sets the "default" to "None" and includes the new "preRequisites" block with the "AMP_vdm-next" feature flag. This implementation is consistent with the overall approach, ensuring that the setting is hidden when the flag is disabled.


167-175: Field Level Specification: Clear Prerequisite Addition.
The changes involving the "Module Specific Multi Select Pick List Field Action Mapping" field correctly add a "preRequisites" block with the same feature flag. This ensures consistency across configuration sections while controlling visibility based on "AMP_vdm-next".

@am6010 am6010 changed the title chore: hide zoho detination setting for vdmv2 chore: hide zoho detination setting for vdmv2 - rev-1473 Feb 28, 2025
@am6010 am6010 changed the title chore: hide zoho detination setting for vdmv2 - rev-1473 chore: hide zoho detination setting for vdmv2 Feb 28, 2025
@@ -140,7 +164,15 @@
"type": "redirect",
"redirectGroupKey": "multiSelectFieldLevelDecision",
"label": "Module Specific Multi Select Pick List Field Action Mapping",
"note": "Map Zoho Multi Select Pick List Field Action To Append or Replace"
"note": "Map Zoho Multi Select Pick List Field Action To Append or Replace",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is the entire section of fields mapping getting hidden ? can you attach screenshots of destination page (with minimized sections) in the PR description

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.

3 participants