Add Note to Explain Search Weight Values

[pykettk]

Description (*)

Adds a note beneath the Search Weight attribute's Storefront Properties input to explain what the values mean.

• See: https://docs.magento.com/user-guide/catalog/search-weighted.html#set-the-search-weight-properties-of-an-attribute

Manual testing scenarios (*)

1. Log into the admin
2. Navigate to Stores -> Attributes -> Product
3. Select any attribute from the grid
4. Open the Storefront Properties options on the left hand side
5. Ensure Use in Search is enabled
6. Observe the note is present beneath the Search Weight option
7. The note should read: 10 is the highest priority/heaviest weighting.

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)

Resolved issues:

1. resolves [Issue] Add Note to Explain Search Weight Values #36646: Add Note to Explain Search Weight Values

[m2-assistant]

Hi @pykettk. Thank you for your contribution
Here are some useful tips 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 Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[pykettk]

@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 re-request them if they don't show in a reasonable amount of time.

[pykettk]

@magento give me test instance

[magento-deployment-service]

Hi @pykettk. Thank you for your request. I'm working on Magento instance for you.

[pykettk]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @pykettk. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @pykettk, here is your Magento Instance: https://ea9494773c3000e781501c5046900cb0.instances.magento-community.engineering
Admin access: https://ea9494773c3000e781501c5046900cb0.instances.magento-community.engineering/admin_2c9f
Login: cea4669e
Password: c7ed9d87a31e

[magento-deployment-service]

Hi @pykettk, here is your Magento Instance: https://5b32710167a78a1002ee2b4ad79453a2.instances.magento-community.engineering
Admin access: https://5b32710167a78a1002ee2b4ad79453a2.instances.magento-community.engineering/admin_5c03
Login: b912a32c
Password: 7829f9d322a7

[pykettk]

Manual Testing

Test Instance

2.4 Develop Instance

[pykettk]

@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 re-request them if they don't show in a reasonable amount of time.

[pykettk]

@magento run Integration 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 re-request them if they don't show in a reasonable amount of time.

[pykettk]

@magento run Functional Tests CE

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[pykettk]

Failing functional tests are unrelated to changes in this PR.

[pykettk]

@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 re-request them if they don't show in a reasonable amount of time.

[pykettk]

@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 re-request them if they don't show in a reasonable amount of time.

[engcom-Delta]

@magento create issue