-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Added optional description field to the <route> tag in webapi.xml #27868
base: 2.5-develop
Are you sure you want to change the base?
Added optional description field to the <route> tag in webapi.xml #27868
Conversation
Hi @o-blinnikov. Thank you for your contribution
For more details, please, review the Magento Contributor Guide documentation. |
As Note, looks like tests failed by the reason we added new field to the schema, have to be fixed |
@magento create issue |
…ns-description # Conflicts: # app/code/Magento/WebapiAsync/Test/Unit/Model/ConfigTest.php # dev/tests/integration/testsuite/Magento/AsynchronousOperations/Model/MassScheduleTest.php
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run all tests |
@magento run Functional Tests B2B |
Hi @nuzil, thank you for the review. |
Moving this PR to on hold since we are not picking up any PRs against the 2.5-develop branch right now. Once we pick it up, we will move it to the appropriate status. |
Description (*)
Currently information on every bulk request is stored in database (magento_bulk table) and has a description field. This description filed is currently autogenerated as "Topic %". Where % - is a queue topic name that used.
Tehnically everything works correctly, but those descriptions are used for display messages for end user in Magento Backend. And this leading to confusion that usually Backend users has no idea what does that mean, especially if Bulk API used, where topic names are auto-generated.
This PR is adding an optional attribute to webapi.xml schema, where users can define API request description. This will allow to use this description for Async/Bulk requests descriptions which will improve user experince.
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
Questions or comments
Contribution checklist (*)
Resolved issues: