Skip to content
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

fix: args updated for Settings API endpoints #2483

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

pronob1010
Copy link
Contributor

@pronob1010 pronob1010 commented Dec 13, 2024

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

args are missing for several endpoints in json schema

Settings API endpoints args are updated.

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

  • New Features
    • Enhanced REST API with required parameters for retrieving settings groups and settings.
    • Improved clarity on API endpoint requirements for better client interactions.

@pronob1010 pronob1010 self-assigned this Dec 13, 2024
Copy link
Contributor

coderabbitai bot commented Dec 13, 2024

Walkthrough

The changes involve modifications to the StoreSettingControllerV2 class in the includes/REST/StoreSettingControllerV2.php file, specifically in the register_routes method. The updates introduce required argument specifications for various REST API routes, enhancing clarity for clients by explicitly defining necessary parameters. The routes affected include those for retrieving settings groups, single settings, and settings fields, each now requiring specific identifiers as mandatory inputs.

Changes

File Change Summary
includes/REST/StoreSettingControllerV2.php Updated register_routes() method to include required args for routes:
- GET /dokan/v2/{rest_base}/{group_id} now requires group_id as a required string parameter.
- GET /dokan/v2/{rest_base}/{group_id}/{id} now requires group_id and id as required string parameters.
- GET /dokan/v2/{rest_base}/{group_id}/{parent_id}/{id} now requires group_id, parent_id, and id as required string parameters.

Possibly related PRs

  • Add $data parameter to dokan_update_vendor hook #2386: The changes in the Manager class regarding the dokan_update_vendor hook may relate to the overall handling of vendor data, which could be relevant to the API enhancements in the StoreSettingControllerV2 class that involve managing settings for vendors.
  • Fix admin fixed commission setting validation #2437: The modifications to the commission validation logic in the Settings class may connect with the API changes in the StoreSettingControllerV2, as both involve ensuring correct data handling and validation for settings related to vendors.
  • Fix commission upgrader #2463: The updates to the commission handling in the Update_Category_Commission, Update_Product_Commission, and Update_Vendor_Commission classes may relate to the API changes in the StoreSettingControllerV2, as both involve managing and validating settings that affect vendor operations.

Suggested labels

QA approved, :+1: Dev Review Done, Needs: Testing

Suggested reviewers

  • shohag121
  • mrabbani

Poem

🐰 In the code where settings dwell,
Parameters now ring a clear bell.
Group IDs and more, all in line,
Making our API simply divine!
With each route defined, we hop with glee,
Clear paths ahead for you and me! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd205f6 and 3e92c68.

📒 Files selected for processing (1)
  • includes/REST/StoreSettingControllerV2.php (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • includes/REST/StoreSettingControllerV2.php

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@pronob1010 pronob1010 added the Needs: Dev Review It requires a developer review and approval label Dec 13, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

🧹 Outside diff range and nitpick comments (2)
includes/REST/StoreSettingControllerV2.php (2)

106-122: Consider enhancing error handling for invalid IDs.

While the argument specifications are correct, consider adding validation to ensure the IDs exist and are valid before processing. This would provide better error messages to API consumers.

Example enhancement:

 public function get_single_settings_field( $request ) {
     $group_id  = $request->get_param( 'group_id' );
     $parent_id = $request->get_param( 'parent_id' );
     $id        = $request->get_param( 'id' );
+    
+    // Validate that the group exists
+    $group = ( new Processor() )->get_settings_group( $group_id );
+    if ( is_wp_error( $group ) ) {
+        return $group;
+    }
+    
+    // Validate that the parent setting exists
+    $parent = ( new Processor() )->get_single_settings( $group_id, $parent_id );
+    if ( is_wp_error( $parent ) ) {
+        return $parent;
+    }
+
     return rest_ensure_response( ( new Processor() )->get_single_settings_field( $group_id, $parent_id, $id ) );
 }

Line range hint 1-275: Consider implementing dependency injection for the Processor class.

The Processor class is instantiated multiple times across different methods. Consider injecting it as a dependency in the constructor for better performance and testability.

Example implementation:

 class StoreSettingControllerV2 extends StoreSettingController {
+    /**
+     * @var Processor
+     */
+    private $processor;
+
+    /**
+     * Constructor.
+     */
+    public function __construct() {
+        parent::__construct();
+        $this->processor = new Processor();
+    }

     // Then replace all new Processor() instances with $this->processor
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 02d4fe1 and fd205f6.

📒 Files selected for processing (1)
  • includes/REST/StoreSettingControllerV2.php (3 hunks)
🔇 Additional comments (2)
includes/REST/StoreSettingControllerV2.php (2)

77-88: LGTM! Parameters match method signature.

The argument specifications for the single settings route are well-defined and align with the get_single_settings method parameters.


53-59: LGTM! Verify route parameter usage.

The argument specification for the settings group route follows WordPress REST API standards and properly defines the required group_id parameter.

Let's verify the group_id parameter usage across the codebase:

✅ Verification successful

Parameter usage verified and properly implemented

The group_id parameter is consistently used across all relevant methods in StoreSettingControllerV2.php, confirming that the argument specification matches its actual usage in the codebase. The parameter is properly retrieved using WordPress's standard get_param() method in all instances.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for group_id parameter usage in PHP files
rg -t php "get_param\(\s*['\"]group_id['\"]\s*\)"

Length of output: 662

Copy link
Member

@mrabbani mrabbani left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Pls review your own PRs
  • Be careful about the text domain.

@@ -68,6 +74,18 @@ public function register_routes() {
'methods' => WP_REST_Server::READABLE,
'callback' => [ $this, 'get_single_settings' ],
'permission_callback' => [ $this, 'get_settings_permission_callback' ],
'args' => [
'group_id' => [
'description' => __( 'Unique identifier for the settings group.', 'dokan' ),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that it is not Unique identifier

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bhai, based on this method, I thought it's a unique identifier. Here, the group existence depended on group_id.

    public function get_settings_group( string $group_id ) {
        $group_exist = $this->search_group( $group_id );

        if ( is_wp_error( $group_exist ) ) {
            return $group_exist;
        }

        $settings = apply_filters( 'dokan_vendor_rest_settings_for' . $group_id . '_page', [] );

        return array_map( [ $this, 'populate_settings_elements' ], $settings );
    }

@mrabbani mrabbani added Needs: Author Reply and removed Needs: Dev Review It requires a developer review and approval labels Dec 17, 2024
@pronob1010 pronob1010 added Review Needed Needs: Dev Review It requires a developer review and approval and removed Needs: Author Reply Review Needed labels Dec 31, 2024
@mrabbani mrabbani added 👍 Dev Review Done and removed Needs: Dev Review It requires a developer review and approval labels Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants