Add a check for the presence of the parameter for the bin/magento downloadable:domains commands

[YevhenZvieriev]

Description

Update to the bin/magento downloadable:domains:add and bin/magento downloadable:domains:remove commands

Upon reviewing the usage of the bin/magento downloadable:domains:add and bin/magento downloadable:domains:remove commands, it was noticed that when these commands are invoked without passing a parameter, nothing happens, and the user receives an unclear outcome.

In this Pull Request, a new feature has been added to display an error message if the parameter is missing. Users will now receive a clear notification that they forgot to pass a parameter when invoking these commands.

Changes

• Added a check for the presence of the parameter for the bin/magento downloadable:domains:add and bin/magento downloadable:domains:remove commands.
• Displayed an appropriate error message if the parameter is missing.

These changes enhance the user experience and prevent the unintended execution of commands without passing the required parameter.

Before:

After:

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @YevhenZvieriev. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[YevhenZvieriev]

@magento run all tests

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

[andrewbess]

Hello @YevhenZvieriev
Thank you for your contribution
Could you please fix code to fix the static test failures
Thank you in advance

[YevhenZvieriev]

@magento run all tests

[YevhenZvieriev]

Hello @andrewbess

After fixing the static test issues, the code is now passing every static test. Kindly take a moment to review the revised version of the PR.

[engcom-Dash]

@magento run all tests

[engcom-Dash]

@magento run all tests