Reverse withdrawal page #2924
Open
Reverse withdrawal page #2924
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…package-using-webpack' into feat/dokan-widthraw-admin-list
…package-using-webpack' into feat/dokan-widthraw-admin-list
…ing, and eligibility conditions - Improved handling for `dokanAdminDashboard.currency` fallback in `Accounting.ts`. - Implemented `processDetails` for detailed render of withdrawal methods. - Replaced custom buttons with `DokanButton` for better consistency. - Added eligibility conditions for bulk actions (approve, cancel, delete). - Introduced `formatPrice` utility for consistent price formatting. - Updated table styling with new borders and rounded corners in SCSS. - Corrected TSPath alias in `tsconfig.json`.
…ancellation, and deletion
# Conflicts: # includes/Admin/Dashboard/Dashboard.php
- Added `VendorAsyncSelect` and `DateRangePicker` components for improved filtering. - Updated SCSS to fix z-index and add relative positioning. - Refactored filter handling logic for better clarity and usability.
- Introduced `AsyncSelect` with payment method filter support. - Enhanced UI components for filtering, including updated placeholders and button styles. - Added `loadPaymentMethods` function to dynamically fetch payment methods. - Improved filter reset functionality with additional cleanup actions.
…ollers - Added `ExportController` and `WithdrawExportController` to manage export functionality. - Registered `WithdrawExportController` with WooCommerce under `withdraws` type. - Created comprehensive usage documentation for the export controller. - Enhanced `REST/Manager` to support export controllers seamlessly.
…integration - Added support for withdraw data export via WooCommerce export system. - Introduced `register_data_endpoint` method to map withdraw export endpoint. - Updated `ExportController` and `WithdrawExportController` for endpoint structure alignment. - Enhanced admin withdraw page with bulk export options and improved pagination.
|
Caution Review failedFailed to post review comments WalkthroughAdds admin dashboard pages for Withdraw and Reverse Withdrawal, integrates WooCommerce-style exports via new REST export controllers and manager wiring, updates dashboard routing and styles, introduces TypeScript config and typings, adjusts currency utilities to support admin context, and tweaks admin CSS script dependencies. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor Admin
participant UI as Admin UI (Withdraw Page)
participant DOK as Dokan ExportController
participant WEXP as WithdrawExportController
participant WC as WC Export Engine
Admin->>UI: Click "Export"
UI->>DOK: POST /dokan/v1/reports/withdraws/export (init)
DOK->>WC: Delegate export job (type=withdraws)
WC-->>DOK: Job queued (export_id)
DOK-->>UI: { export_id }
loop Poll status
UI->>DOK: GET /dokan/v1/reports/withdraws/export/status?export_id
DOK->>WC: Fetch job status
WC-->>DOK: { status, file_url? }
DOK-->>UI: { status, file_url? }
end
alt Completed
UI->>WC: Download file_url
WC-->>UI: CSV file
else Error
DOK-->>UI: Error response
end
sequenceDiagram
autonumber
actor Admin
participant UI as Admin UI (Reverse Withdrawal)
participant API as REST API
note over UI,API: Add Reverse Withdrawal Transaction
Admin->>UI: Open "Add New" modal
Admin->>UI: Select vendor/product/order, type, amount, note
UI->>API: POST /dokan/v1/reverse-withdrawal/transactions {payload}
alt Success
API-->>UI: 201 Created
UI->>UI: Close modal, refresh list
else Validation/Error
API-->>UI: 4xx/5xx
UI->>Admin: Show inline errors
end
Estimated code review effort🎯 4 (Complex) | ⏱️ ~75 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
Pre-merge checks and finishing touches and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
🧪 Generate unit tests
✨ Finishing touches
🧪 Generate unit tests
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. 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. Comment |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
All Submissions:
Changes proposed in this Pull Request:
Related Pull Request(s)
Closes
How to test the changes in this Pull Request:
Changelog entry
Title
Detailed Description of the pull request. What was previous behaviour
and what will be changed in this PR.
Before Changes
Describe the issue before changes with screenshots(s).
After Changes
Describe the issue after changes with screenshot(s).
Feature Video (optional)
Link of detailed video if this PR is for a feature.
PR Self Review Checklist:
FOR PR REVIEWER ONLY:
Summary by CodeRabbit
New Features
Documentation
Style
Bug Fixes