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

Plugins: Move misplaced return statement in wp_get_plugin_action_button(). #6757

Conversation

costdev
Copy link
Contributor

@costdev costdev commented Jun 7, 2024

@costdev costdev force-pushed the move_return_line_in_wp_get_plugin_action_button branch 5 times, most recently from 013005a to ba52028 Compare June 7, 2024 16:47
Copy link

github-actions bot commented Jun 7, 2024

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@costdev costdev force-pushed the move_return_line_in_wp_get_plugin_action_button branch from ba52028 to 2a6aa85 Compare June 7, 2024 17:03
@costdev costdev force-pushed the move_return_line_in_wp_get_plugin_action_button branch from 2a6aa85 to 3260652 Compare June 7, 2024 17:06
@costdev costdev marked this pull request as ready for review June 7, 2024 18:39
Copy link

github-actions bot commented Jun 7, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props costdev, hellofromtonya.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@costdev costdev force-pushed the move_return_line_in_wp_get_plugin_action_button branch from dfcf36d to 3010506 Compare June 9, 2024 01:40

self::$role = get_role( $role_name );
self::$user_id = self::factory()->user->create( array( 'role' => $role_name ) );
self::$test_plugin = (object) array(
Copy link
Contributor

Choose a reason for hiding this comment

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

This approach works well for the specific needs of this ticket and the issue it addresses. That said, the function under test will need additional plugin mashups (i.e. different $data) for its various test scenarios.

It might be good to start off with a helper function that builds / creates the plugin for each test.

Is there already examples / usage within the test suite? Yes.

Example, WP_REST_Plugins_Controller_Test::create_test_plugin().

What do you think @costdev?

Copy link
Contributor

Choose a reason for hiding this comment

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

The more I think about this -> let's tackle it when adding more tests. The current approach is within scope for this ticket.

Copy link
Contributor

@hellofromtonya hellofromtonya left a comment

Choose a reason for hiding this comment

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

LGTM 👍 Ready for commit

@hellofromtonya
Copy link
Contributor

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.

2 participants