Hello! 👋

Thanks for opening this pull request! Please check out our contributing guidelines. We appreciate you taking the initiative to contribute to this project.

Contributing isn't limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation.

Here are some useful Composer commands to get you started:

• composer install: Install dependencies.
• composer test: Run the full test suite.
• composer phpcs: Check for code style violations.
• composer phpcbf: Automatically fix code style violations.
• composer phpunit: Run unit tests.
• composer behat: Run behavior-driven tests.

To run a single Behat test, you can use the following command:

# Run all tests in a single file
composer behat features/some-feature.feature

# Run only a specific scenario (where 123 is the line number of the "Scenario:" title)
composer behat features/some-feature.feature:123

You can find a list of all available Behat steps in our handbook.

720ded9

Thanks for your PR.

Haven't looked at the code or the failing test yet, but a quick question:

How is "wp sidebar widgets" different from the already existing "wp widget list" command? We don't want to duplicate functionality.

@swissspidy

• wp widget list

  • What it does:
    • Lists all available widget types on the site.
  • Think of it as:
    • “What widgets exist and can be used?”

• wp sidebar widgets

  • What it does:
    • Shows which widgets are actually assigned to sidebars.
  • Think of it as:
    • “Which widgets are currently in use and where?”

I'm afraid that's incorrect. Have you tried using & comparing the two commands?

wp widget list lists widgets associated with a sidebar (using wp_get_sidebars_widgets(). You get the widget name, ID, position, etc.

@swissspidy

0e6d9d1

Codecov Report

❌ Patch coverage is 0% with 14 lines in your changes missing coverage. Please review.

📢 Thoughts on this report? Let us know!

This is still lacking test coverage. If you could add Behat tests for these new commands I'll happily take a look.