feat: React Skeleton and Vendor withdraw by shohag121 · Pull Request #2403 · getdokan/dokan

shohag121 · 2024-10-17T08:31:14Z

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:

Related Pull Request(s)

Closes

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

How to test the changes in this Pull Request:

Please check if flash rewrite rules need to be updated or not just after switching into this branch.

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:

Code is not following code style guidelines
Bad naming: make sure you would understand your code if you read it a few months from now.
KISS: Keep it simple, Sweetie (not stupid!).
DRY: Don't Repeat Yourself.
Code that is not readable: too many nested 'if's are a bad sign.
Performance issues
Complicated constructions that need refactoring or comments: code should almost always be self-explanatory.
Grammar errors.

FOR PR REVIEWER ONLY:

As a reviewer, your feedback should be focused on the idea, not the person. Seek to understand, be respectful, and focus on constructive dialog.

As a contributor, your responsibility is to learn from suggestions and iterate your pull request should it be needed based on feedback. Seek to collaborate and produce the best possible contribution to the greater whole.

Correct — Does the change do what it’s supposed to? ie: code 100% fulfilling the requirements?
Secure — Would a nefarious party find some way to exploit this change? ie: everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities?
Readable — Will your future self be able to understand this change months down the road?
Elegant — Does the change fit aesthetically within the overall style and architecture?

Summary by CodeRabbit

Based on the comprehensive summary, here are the updated release notes:

New Features
- Added a new Status page in the admin dashboard with dynamic content rendering.
- Introduced DataView Table component for flexible data management.
- Implemented a Sortable List component with drag-and-drop functionality.
- Enhanced dashboard navigation with React routing capabilities.
- Added new REST API endpoints for managing continents and countries.
- Introduced new components for status elements, including Button, Heading, Link, and more.
- Added new useWindowDimensions hook for tracking viewport dimensions.
- Introduced VendorNavMenuChecker for managing vendor dashboard navigation.
- Added NewDashboard class for custom dashboard templates.
- Enhanced withdrawal management with new components and hooks for handling requests and balances.
- Added a new Filter component for standardized filtering operations.
- Introduced DokanModal for customizable modal dialogs.
Improvements
- Updated REST API endpoints for customers, continents, and countries.
- Enhanced the integration of React components and styles into the asset management system.
- Improved error handling and loading states across various components.
Technical Updates
- Upgraded Tailwind CSS configuration.
- Updated webpack entry points and configuration.
- Added new dependencies for improved functionality.
- Extended the global Window interface for better type safety in TypeScript.
Documentation
- Added comprehensive documentation for components, hooks, and utilities.
- Provided implementation guides for new features.
- Enhanced documentation for the DataView Table and Sortable List components.
- Updated documentation for defining menus and managing PHP overrides in React applications.
- Introduced guidelines for creating filter and slot documentation.

This commit introduces a new REST API endpoint for searching customers specific to a vendor's orders. Key changes include: - Add new route `/dokan/v1/customers/search` in CustomersController - Implement `search_customers` method with the following features: * Search customers by ID or term (name/email) * Limit results to customers who have ordered from the current vendor * Support excluding specific customer IDs * Limit results to 20 when search term is less than 3 characters * Apply `dokan_json_search_found_customers` filter for extensibility - Add permission check to ensure only users with 'edit_shop_orders' capability can access - Include detailed PHPDoc for the new filter This feature allows vendors to efficiently search their customer base through the REST API, mirroring the functionality of the existing AJAX action while providing a standardized API interface.

…ure' into update/vendor-dashboard-structure

…e' into update/vendor-dashboard-structure

…ses for Customer API

…er-api' into update/vendor-dashboard-structure # Conflicts: # includes/REST/Manager.php

…shboard-structure

shashwatahalder01 · 2025-02-14T06:07:00Z

Scenario:
Loader Icon Appears on Both Buttons in Withdrawal Request Cancel Modal

Screenshot:

shashwatahalder01 · 2025-02-14T08:48:54Z

Scenario:
Request Withdraw Button Displays Insufficient Balance Warning Despite Sufficient Funds.

On the "View Payments" page, clicking the Request Withdraw button triggers an "Insufficient Balance" warning message, even when the vendor's account balance exceeds the minimum withdrawal restriction.

Steps to reproduce:

Navigate to vendor > withdraw > view payments page
Click withdraw button on the "View Payments" page.

Screencast

shashwatahalder01 · 2025-02-14T09:18:02Z

Scenario:
console error on the withdraw page

Screenshot:

shashwatahalder01 · 2025-02-14T09:31:12Z

Scenario:
Console Error When Submitting Withdrawal Request Below Minimum Amount on First Attempt

When a user attempts to submit a withdrawal request for an amount below the minimum required amount, a console error occurs on the first attempt.

Steps to Reproduce:

Navigate to Withdraw Page
Enter an amount below the minimum withdrawal limit (e.g., enter $50 when the minimum is $100).
Click the Submit or Request Withdraw button.
Observe Console
Navigate away from the withdrawal page (e.g., go to the Dashboard or another section). and then return back to the withdrawal page.
Repeat steps 2 to 4 to observe if the error persists.

Screenshot:

shashwatahalder01 · 2025-02-14T10:59:59Z

Scenario:
There is no close button on the withdraw disbursement modal window

Screenshot:

Aunshon · 2025-02-26T11:04:58Z

Scenario: Console Error When Submitting Withdrawal Request Below Minimum Amount on First Attempt

When a user attempts to submit a withdrawal request for an amount below the minimum required amount, a console error occurs on the first attempt.

Steps to Reproduce:

Navigate to Withdraw Page

Enter an amount below the minimum withdrawal limit (e.g., enter $50 when the minimum is $100).

Click the Submit or Request Withdraw button.

Observe Console

Navigate away from the withdrawal page (e.g., go to the Dashboard or another section). and then return back to the withdrawal page.

Repeat steps 2 to 4 to observe if the error persists.

Screenshot:

@shashwatahalder01 vai we will ignore this error for now, this issue occered for Dokan UI i have discussed with @mrabbani vai about it.

Fix loader when cancel withdraw request.

…le contents. (#2546) * enhance: Introduce DokanModal component. * enhance: Update dokan src package root name. * fix: remove unused code. * enhance: Expand sortable list feature, handle pointer & elements. * fix: remove dokan modal & add params with header slot.

feat: React Skeleton

a2701f5

shohag121 assigned shohag121 and Aunshon Oct 17, 2024