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

On slack,discord add support for Include hidden fields #654

Merged

Conversation

chiragchhatrala
Copy link
Collaborator

@chiragchhatrala chiragchhatrala commented Dec 19, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a toggle switch for including hidden fields in notification messages.
    • Enhanced webhook data handling for both Discord and Slack integrations to optionally include hidden fields based on user settings.
  • Bug Fixes

    • Updated initialization logic to ensure new properties are set to default values if undefined.
  • Documentation

    • Updated validation rules for webhook submissions to include a new option for hidden fields.

Copy link
Contributor

coderabbitai bot commented Dec 19, 2024

Walkthrough

This pull request introduces a new feature for Discord and Slack integrations that allows optional inclusion of hidden fields in form submission notifications. The changes span across three files: DiscordIntegration.php, SlackIntegration.php, and NotificationsMessageActions.vue. A new validation rule and configuration option include_hidden_fields_submission_data has been added, enabling users to control the visibility of hidden fields in webhook messages.

Changes

File Change Summary
api/app/Integrations/Handlers/DiscordIntegration.php Added include_hidden_fields_submission_data validation rule and updated getWebhookData method to conditionally include hidden fields
api/app/Integrations/Handlers/SlackIntegration.php Added include_hidden_fields_submission_data validation rule and updated getWebhookData method to conditionally include hidden fields
client/components/open/integrations/components/NotificationsMessageActions.vue Added toggle switch for include_hidden_fields_submission_data and initialized the property in the created lifecycle hook

Sequence Diagram

sequenceDiagram
    participant User
    participant NotificationsUI
    participant Integration
    participant FormSubmissionFormatter

    User->>NotificationsUI: Configure hidden fields option
    NotificationsUI->>Integration: Set include_hidden_fields_submission_data
    Integration->>FormSubmissionFormatter: Call showHiddenFields() if enabled
    FormSubmissionFormatter-->>Integration: Return submission data with hidden fields
    Integration->>User: Send webhook with optional hidden fields
Loading

Possibly related PRs

Suggested reviewers

  • JhumanJ

Poem

🐰 Webhooks dancing, hidden fields in sight,
A toggle switch brings data's delight!
Discord and Slack now whisper more,
Revealing secrets they once bore.
Integration magic, rabbit's glee! 🎉


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

@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)
client/components/open/integrations/components/NotificationsMessageActions.vue (1)

105-106: Consider adding a warning message for hidden fields

While the implementation is correct, consider adding a warning message when enabling hidden fields, as they might contain sensitive information.

 } else if (['include_hidden_fields_submission_data'].includes(keyname)) {
   this.compVal[keyname] = false
+  if (this.compVal[keyname]) {
+    this.$emit('warning', 'Hidden fields may contain sensitive information. Please review your form\'s hidden fields before enabling this option.')
+  }
 }
api/app/Integrations/Handlers/SlackIntegration.php (1)

18-18: Consider abstracting common integration logic

While the implementation is correct and consistent with DiscordIntegration, there's duplicate code for handling hidden fields. Consider moving this logic to the AbstractIntegrationHandler.

// In AbstractIntegrationHandler.php
+ protected function getFormattedSubmissionData(): array {
+     $settings = (array) $this->integrationData ?? [];
+     $formatter = (new FormSubmissionFormatter($this->form, $this->submissionData))
+         ->outputStringsOnly();
+     
+     if (Arr::get($settings, 'include_hidden_fields_submission_data', false)) {
+         $formatter->showHiddenFields();
+     }
+     
+     return $formatter->getFieldsWithValue();
+ }

// In DiscordIntegration.php and SlackIntegration.php
- $settings = (array) $this->integrationData ?? [];
- $formatter = (new FormSubmissionFormatter($this->form, $this->submissionData))->outputStringsOnly();
- if (Arr::get($settings, 'include_hidden_fields_submission_data', false)) {
-     $formatter->showHiddenFields();
- }
- $formattedData = $formatter->getFieldsWithValue();
+ $formattedData = $this->getFormattedSubmissionData();

Also applies to: 38-43

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d18c4cc and bbf77ee.

📒 Files selected for processing (3)
  • api/app/Integrations/Handlers/DiscordIntegration.php (2 hunks)
  • api/app/Integrations/Handlers/SlackIntegration.php (2 hunks)
  • client/components/open/integrations/components/NotificationsMessageActions.vue (3 hunks)
🔇 Additional comments (4)
client/components/open/integrations/components/NotificationsMessageActions.vue (1)

18-25: LGTM! Clear and consistent UI implementation

The toggle switch for hidden fields is well-implemented with:

  • Clear labeling and helpful description
  • Proper conditional rendering based on include_submission_data
  • Consistent styling with other toggle switches
api/app/Integrations/Handlers/DiscordIntegration.php (2)

18-18: LGTM! Proper validation rule implementation

The validation rule correctly allows for nullable boolean values, maintaining consistency with the frontend implementation.


38-43: Verify hidden fields handling in FormSubmissionFormatter

The implementation looks correct, but we should verify the FormSubmissionFormatter's handling of hidden fields.

✅ Verification successful

Hidden fields handling in FormSubmissionFormatter is properly implemented

The implementation is correct and thorough. The FormSubmissionFormatter class:

  • Has a showHiddenFields flag that defaults to false
  • Properly checks this flag in both getCleanKeyValue() and getFieldsWithValue() methods
  • Uses FormLogicPropertyResolver::isHidden() to determine if fields should be hidden
  • Skips hidden fields when the flag is false and includes them when true
  • Maintains chainable method pattern for configuration
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for FormSubmissionFormatter's showHiddenFields implementation
ast-grep --pattern 'class FormSubmissionFormatter {
  $$$
  public function showHiddenFields() {
    $$$
  }
  $$$
}'

Length of output: 119


Script:

#!/bin/bash
# Let's try a broader search for FormSubmissionFormatter class and its implementation
rg -l "class FormSubmissionFormatter"

# Then search for showHiddenFields method across the codebase
rg "showHiddenFields"

# Also search for hidden fields related functionality
rg "hidden.*fields" -i

Length of output: 68267


Script:

#!/bin/bash
# Let's get the content of FormSubmissionFormatter.php to verify the implementation
cat api/app/Service/Forms/FormSubmissionFormatter.php

Length of output: 10583

api/app/Integrations/Handlers/SlackIntegration.php (1)

38-43: Verify consistent behavior across integrations

Let's verify that both Discord and Slack integrations handle hidden fields identically.

✅ Verification successful

Hidden fields handling is consistent across Discord and Slack integrations

Both Discord and Slack integrations handle hidden fields in exactly the same way:

  1. Both use the same FormSubmissionFormatter class
  2. Both check the include_hidden_fields_submission_data setting using Arr::get($settings, 'include_hidden_fields_submission_data', false)
  3. Both call showHiddenFields() on the formatter when the setting is enabled
  4. Both use getFieldsWithValue() to retrieve the formatted data

The implementations are identical in terms of hidden fields handling, ensuring consistent behavior across both integrations.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Compare the implementation of hidden fields handling
diff <(rg -A 5 'include_hidden_fields_submission_data' api/app/Integrations/Handlers/DiscordIntegration.php) <(rg -A 5 'include_hidden_fields_submission_data' api/app/Integrations/Handlers/SlackIntegration.php)

Length of output: 318


Script:

#!/bin/bash
# Let's first check if both integration files exist and examine their content
echo "=== Checking Discord Integration ==="
rg -A 10 "FormSubmissionFormatter" api/app/Integrations/Handlers/DiscordIntegration.php || echo "No matches found"

echo -e "\n=== Checking Slack Integration ==="
rg -A 10 "FormSubmissionFormatter" api/app/Integrations/Handlers/SlackIntegration.php || echo "No matches found"

Length of output: 2254

@JhumanJ JhumanJ merged commit 9a2d7b9 into main Dec 30, 2024
5 checks passed
@JhumanJ JhumanJ deleted the 161a6-on-integration-add-option-for-include-hidden-fields branch December 30, 2024 10:11
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.

2 participants