Skip to content

Conversation

akzmoudud
Copy link
Contributor

@akzmoudud akzmoudud commented Sep 4, 2025

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)

  • Full PR Link

Closes

How to test the changes in this Pull Request:

  • Steps or issue link

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?

Copy link
Contributor

coderabbitai bot commented Sep 4, 2025

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.

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

✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat/reverse-withdraw-react

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

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

@akzmoudud akzmoudud self-assigned this Sep 9, 2025
kzamanbd and others added 7 commits September 10, 2025 17:42
Exposes useSearchParams and useParams from react-router-dom in the withRouter HOC context, allowing wrapped components to access search and route parameters more easily.
* feat: Add DateRangePicker component for selecting date ranges with customizable options

* feat: Implement DateRangePicker component with customizable date selection

* refactor: Rename DateRangePicker files and update component props handling

---------

Co-authored-by: Mahbub Rabbani <[email protected]>
Updated the vendor selection field in the WooCommerce product quick edit to use a dynamic select input with AJAX search, improving scalability and user experience. Exposed DokanAdminProduct to the global window object for use in inline edit scripts. Minor code cleanup and improved event handling for inline edit actions.
Deleted the DateRangePicker component and its associated SCSS file. Also removed its export from the components index. This cleans up unused code and dependencies related to date range picking.
@akzmoudud akzmoudud added the Needs: Testing This requires further testing label Sep 12, 2025
mrabbani and others added 8 commits September 12, 2025 18:44
* refactor: Remove the global mutation observer

* fix: ensure headlessui portal is visible by setting display to block in DokanModal

* fix: simplify modal components by removing redundant styles and adding callbacks

* fix: remove unused tailwind-merge import from DokanModal

* fix: rename `className` to `modalClassName` in `DokanModal` and update usage in related components

* fix: use twMerge to merge modal class names in DokanModal for cleaner style management

* fix: remove unused Modal import from VideoPopup module

* fix: replace Modal with DokanModal and refactor props for better customization and consistency across components

* fix: move onChange handler directly to TextArea for cleaner implementation

* Update popover component. (#2797)

* feat: add custom Popover component using WordPress UI

* feat: integrate Popover component into WpDatePicker for enhanced date selection

* feat: enhance CategorySelector with custom Popover for category selection

* fix: wcAdmin settings null exception for the vendor dashboard

* fix: Modal usage

* fix: add modalFooterClassName prop to DokanModal for customizable footer styling

* feat: Implement DokanTooltip and use it across the system. (#2900)

* fix: set portalTarget for Select component to ensure proper rendering

---------

Co-authored-by: Al Amin Ahamed <[email protected]>
Co-authored-by: Aunshon <[email protected]>
Co-authored-by: Md Asif Hossain Nadim <[email protected]>
Co-authored-by: Md. Asif Hossain Nadim <[email protected]>
@akzmoudud akzmoudud removed the Needs: Testing This requires further testing label Sep 18, 2025
@akzmoudud akzmoudud added Needs: Dev Review It requires a developer review and approval Needs: Testing This requires further testing labels Sep 19, 2025
@akzmoudud
Copy link
Contributor Author

@akzmoudud akzmoudud force-pushed the feat/reverse-withdraw-react branch from 37ee3f8 to 4b58a11 Compare September 29, 2025 07:08
@akzmoudud akzmoudud removed Needs: Dev Review It requires a developer review and approval Needs: Testing This requires further testing labels Sep 30, 2025
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.

8 participants