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

Enhance Form Submission Export Functionality #657

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

chiragchhatrala
Copy link
Collaborator

@chiragchhatrala chiragchhatrala commented Jan 2, 2025

Summary by CodeRabbit

  • New Features

    • Enhanced form submission export functionality
    • Added ability to select specific columns for CSV export
  • Changes

    • Modified export route from GET to POST request
    • Updated export method to accept column selection parameters
  • Improvements

    • Increased flexibility in form submission data export process
    • More granular control over exported data columns

Copy link
Contributor

coderabbitai bot commented Jan 2, 2025

Walkthrough

The pull request introduces changes to the form submission export functionality across multiple files. The modifications allow for more dynamic control over exported data by enabling users to specify which columns should be included in the CSV export. The changes involve updating the FormSubmissionController, modifying the API route from GET to POST, and adjusting the client-side component to support the new export mechanism.

Changes

File Change Summary
api/app/Http/Controllers/Forms/FormSubmissionController.php Updated method signature to accept Request, added $displayColumns to filter export columns dynamically
api/routes/api.php Changed export route from GET to POST method
client/components/open/forms/components/FormSubmissions.vue Modified exportUrl and downloadAsCsv method to support POST request with column selection

Sequence Diagram

sequenceDiagram
    participant Client as Form Submissions Component
    participant API as Export Controller
    participant Database as Form Data Storage

    Client->>API: POST /submissions/export
    API->>Database: Retrieve Form Submissions
    API-->>Client: CSV with Selected Columns
Loading

Poem

🐰 Hop, hop, export with glee!
Columns dance, now wild and free
POST request brings magic's might
CSV sparkles, data's delight
Flexible export, rabbit's design 🌟


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. (Beta)
  • @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)
api/app/Http/Controllers/Forms/FormSubmissionController.php (1)

64-75: Dynamic column export logic looks solid.
Filtering and mapping columns to $filteredData based on $displayColumns is a neat approach. However, consider validating the existence of $column keys in your $formattedData to avoid edge cases if the request or data changes.

client/components/open/forms/components/FormSubmissions.vue (1)

336-342: POST request with column data fosters flexibility but requires server validation.
The new body parameter enhances dynamic exports. Ensure the backend enforces security checks and handles empty or large columns arrays gracefully.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2366f95 and 960c9d2.

📒 Files selected for processing (3)
  • api/app/Http/Controllers/Forms/FormSubmissionController.php (2 hunks)
  • api/routes/api.php (1 hunks)
  • client/components/open/forms/components/FormSubmissions.vue (2 hunks)
🔇 Additional comments (7)
api/app/Http/Controllers/Forms/FormSubmissionController.php (5)

17-17: Good addition of the Request import for improved handling of input data.
This import is essential for the enhanced export functionality.


50-50: Method signature update is aligned with the POST approach.
The change from public function export(string $id) to public function export(Request $request, string $id) allows dynamic input parameters.


56-56: Security check: Validate $request->columns before usage.
Ensure the request contains the expected data type (array) and handle any malformed input to prevent errors or potential injection.


81-81: Filename customization is clear and consistent with this approach.
Appending -submission-data.csv is straightforward and improves clarity.


88-89: Check for consistency in file paths.
The dynamic file path is carefully constructed. Ensure consistency with the rest of your file downloads to avoid confusion around leading/trailing slashes.

client/components/open/forms/components/FormSubmissions.vue (1)

216-216: Removing the leading slash is correct for consistent routing.
Make sure your other API calls also follow the same pattern if needed.

api/routes/api.php (1)

164-164: Switching from GET to POST aligns with sending request payload.
This ensures that large or sensitive data can be provided without URL length constraints and is more secure.

Copy link
Owner

@JhumanJ JhumanJ left a comment

Choose a reason for hiding this comment

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

Please improve back-end validation

@@ -46,38 +47,46 @@ public function update(AnswerFormRequest $request, $id, $submissionId)
]);
}

public function export(string $id)
public function export(Request $request, string $id)
Copy link
Owner

Choose a reason for hiding this comment

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

Need to validate the new param you added

{
$form = Form::findOrFail((int) $id);
$this->authorize('view', $form);

$allRows = [];
$displayColumns = collect($request->columns)->filter(fn ($value, $key) => $value === true)->toArray();
Copy link
Owner

Choose a reason for hiding this comment

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

need to ensure the column exist in the form

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