-
Notifications
You must be signed in to change notification settings - Fork 319
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
base: main
Are you sure you want to change the base?
Conversation
WalkthroughThe 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 Changes
Sequence DiagramsequenceDiagram
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
Poem
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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 largecolumns
arrays gracefully.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 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 frompublic function export(string $id)
topublic 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.
There was a problem hiding this 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) |
There was a problem hiding this comment.
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(); |
There was a problem hiding this comment.
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
Summary by CodeRabbit
New Features
Changes
Improvements