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

[33099] Set admin field as required while creating Visual Swatch attribute #33795

Merged
merged 5 commits into from Jun 14, 2022

Conversation

Usik2203
Copy link
Contributor

@Usik2203 Usik2203 commented Aug 13, 2021

Description (*)

120062326-cdc29280-c08b-11eb-91ae-19264fe6c290

Based on exception in console with message "Admin is a required field in each row" admin is a required field.
This PR set admin field as required

Actual result

Screenshot 2021-08-13 at 18 32 24

Fixed Issues (if relevant)

  1. Fixes Not showing error message when create attribute at product page #33099

Manual testing scenarios (*)

  1. Admin -> Catalog -> Product -> Add new product -> Add Attribute -> Create New Attribute
  2. Fill Attribute Label -> Choose Catalog Input Type for Store Owner is Vitual Swatch -> Manage Swatch -> Add Swatch -> Fill Default Store View -> Save Attribute

@m2-assistant
Copy link

m2-assistant bot commented Aug 13, 2021

Hi @Usik2203. 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

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

@m2-community-project m2-community-project bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Aug 13, 2021
@magento-engcom-team magento-engcom-team added Area: Frontend Component: Swatches Release Line: 2.4 Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner labels Aug 13, 2021
@Usik2203 Usik2203 changed the title [33099] set admin field as requaired [33099] Set admin field as requaired while creating Visual Swatch attribute Aug 13, 2021
@Usik2203
Copy link
Contributor Author

@magento run all tests

@magento-automated-testing
Copy link

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.

@shikhamis11 shikhamis11 self-requested a review August 14, 2021 14:46
@shikhamis11
Copy link
Member

@Usik2203 thank you for your Pull request. It seems a similar error message is showing for Text Swatch too, Would you mind fixing it for Text Swatches as well ? Also Please cover your changes with MFTF test.

Copy link
Member

@shikhamis11 shikhamis11 left a comment

Choose a reason for hiding this comment

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

@engcom-Bravo
Copy link
Contributor

@Usik2203 @shikhamis11 Thanks for your contribution!
@Usik2203 I am working on the requested changes.

@engcom-Bravo engcom-Bravo self-assigned this Sep 2, 2021
@engcom-Bravo
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

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-Bravo
Copy link
Contributor

Hi @shikhamis11 ,

I have worked on the requested changes by you.

Requesting you for review.

Thank You!

@engcom-Bravo engcom-Bravo moved this from Changes Requested to Pending Review in High Priority Pull Requests Dashboard Sep 7, 2021
@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

Preconditions:

  1. Have a Magento latest instance installed with sample data

Manual testing scenario:

  1. Admin - Catalog - Product - Click on Create a new simple product.

  2. Click on "New Attribute" button from the Product form page.

  3. Try to create new configuration attribute with the type "Text Swatch" or "Visual Swatch" keeping admin field empty.

Before: ✖️ Admin field was not being validated while creating a new attribute from new product creation page
image

After: ✔️ Admin field is being validated while creating a new attribute from new product creation page

image

There is no impact on any other feature since it is relevant to a particular field validation in the UI. Also cross checked that the automation failures is not because of PR changes!

@engcom-Alfa engcom-Alfa moved this from Testing in Progress to Merge in Progress in High Priority Pull Requests Dashboard Sep 17, 2021
@sidolov sidolov moved this from Merge in Progress to Extended Testing (optional) in High Priority Pull Requests Dashboard Oct 7, 2021
@engcom-Charlie engcom-Charlie self-assigned this Oct 25, 2021
@m2-community-project m2-community-project bot moved this from Extended Testing (optional) to Ready for Testing in High Priority Pull Requests Dashboard Oct 25, 2021
@engcom-Charlie engcom-Charlie removed their assignment Oct 25, 2021
@engcom-Charlie
Copy link
Contributor

It seems that bot automatically moved this PR from Extended Testing to Ready for testing, so moving back to Extended Testing.

@engcom-Charlie engcom-Charlie self-assigned this Oct 25, 2021
@engcom-Charlie engcom-Charlie moved this from Ready for Testing to Extended Testing (optional) in High Priority Pull Requests Dashboard Oct 25, 2021
@engcom-Charlie
Copy link
Contributor

The test case which is failing in this build is related to currency converter API. The build failure is not because of the PR changes and hence moving this to Merge in Progress.

Thank you!

@engcom-Charlie engcom-Charlie moved this from Extended Testing (optional) to Merge in Progress in High Priority Pull Requests Dashboard Nov 8, 2021
@ishakhsuvarov
Copy link
Contributor

@magento run all tests

@magento-automated-testing
Copy link

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.

@ishakhsuvarov
Copy link
Contributor

@magento run Functional Tests CE, Functional Tests B2B

@magento-automated-testing
Copy link

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.

@magento-devops-reposync-svc magento-devops-reposync-svc merged commit 8a89643 into magento:2.4-develop Jun 14, 2022
@ishakhsuvarov ishakhsuvarov moved this from Merge in Progress to Recently Merged in High Priority Pull Requests Dashboard Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Frontend Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Award: bug fix Component: Catalog Component: Swatches Partner: Atwix Pull Request is created by partner Atwix partners-contribution Pull Request is created by Magento Partner Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Release Line: 2.4
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Not showing error message when create attribute at product page
9 participants