enhance: migrate admin Reverse Withdrawal tables to Plugin UI DataViews

[MdAsifHossainNadim]

All Submissions:

• My code follow the WordPress' coding standards
• My code satisfies feature requirements
• My code is tested
• My code passes the PHPCS tests
• My code has proper inline documentation
• I've included related pull request(s) (optional)
• I've included developer documentation (optional)
• I've added proper labels to this pull request

Changes proposed in this Pull Request:

Migrates both admin Reverse Withdrawal tables to the unified DataViews component re-exported from @dokan/components:

• dokan/src/admin/dashboard/pages/reverse-withdrawal/index.tsx — main reverse-withdrawal list.
• dokan/src/admin/dashboard/pages/reverse-withdrawal/ReverseWithdrawalTransaction.tsx — drill-down transactions table.

Per page:

• Drops the AdminDataViews as DataViews alias in favour of the direct DataViews import.
• Status state lives in view.status (no separate activeTab mirror).
• Tabs reshape: { tabs: [{ name, title, icon }] } → { items: [{ value, label, count }] }.
• Removes the stray "List of Data" tab that the legacy wrapper required as a placeholder; the funnel filter button still appears via plugin-ui's built-in headerContent. The list page no longer passes a tabs={…} prop at all.
• Filter prop unchanged — { id, label, field } shape carries over directly.
• Wraps <DataViews> in <div className="dokan-admin-dashboard-datatable"> so existing SCSS keeps applying.

Wrapper-component swap, not a redesign — stats cards, funnel filter, sorting, pagination, vendor drill-down, transaction table all preserved.

Related Pull Request(s)

• Parent: enhance: migrate admin dashboard list tables to Plugin UI DataViews #3192

Closes

• Closes https://github.com/getdokan/plugin-internal-tasks/issues/1848

How to test the changes in this Pull Request:

1. Build assets: npm run build.
2. WP Admin → Dokan → Reverse Withdrawal.
3. Confirm the four stats cards still render at the top.
4. Confirm there is no stray "List of Data" tab on the table.
5. Use the funnel filter button (top-right of the table card) — chips render, Reset clears.
6. Click into a vendor row to open the transactions drill-down — confirm the transactions table loads and paginates.
7. Resize to mobile width — both tables collapse to list view.
8. Confirm both tables share the single white card with the funnel button on the right.

Changelog entry

Migrate admin Reverse Withdrawal tables to Plugin UI DataViews

Replaces the legacy AdminDataViews wrapper on both admin Reverse Withdrawal tables (main list + transaction drill-down) with the unified DataViews component. Drops the placeholder "List of Data" tab the legacy wrapper required. Stats cards, funnel filter, sorting, pagination, and the vendor → transactions drill-down all behave the same.

Before Changes

Both Reverse Withdrawal tables used the in-house AdminDataViews wrapper, which forced a single placeholder "List of Data" tab to render. Tabs and filter sat outside the table card.

After Changes

Both tables use DataViews from @wedevs/plugin-ui. The placeholder tab is gone. Funnel filter button + table render inside a single white card matching the rest of the admin dashboard.

Feature Video (optional)

n/a

PR Self Review Checklist:

• Follows WPCS / project conventions.
• Removed dead helpers (the synthetic tabItems array and the tabs={…} prop on the list page).
• DRY — both files share the same migration pattern; no duplicate helpers introduced.

FOR PR REVIEWER ONLY:

• Correct — funnel filter, sorting, pagination, vendor drill-down all still work; placeholder tab removed.
• Secure — no new escaping concerns; reuses existing reverse-withdrawal REST endpoints.
• Readable — diff is small per file (import swap, view.status, tabs prop removed).
• Elegant — cleanly drops legacy wrapper without behavioural changes.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 21213b5c-0194-4c13-b5d1-68f8edebd533

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch enhance/update-admin-dashboard-reverse-withdrawal-list-tables

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}