Skip to content

Fixed issue regarding widget form validation #23499

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

Closed
wants to merge 23 commits into from

Conversation

yash7690
Copy link

@yash7690 yash7690 commented Jun 29, 2019

Description (*)

-> Have added attribute to provide additional_classes in xml file, so that field in widget can have validation classes like integer, positive-integer, validate-zero-or-greater etc
-> Have created a new validation rule for "Not negative integer" validation

Fixed Issues (if relevant)

Widget form was not having any validation apart from required. Have added additional_classes attribute to field so that any class/validation can apply.

  1. Fixes Usage of non-numeric value for "Number of Products to Display" setting in "Catalog Products List" widget leads to an exception #23422: Usage of non-numeric value for "Number of Products to Display" setting in "Catalog Products List" widget leads to an exception

Manual testing scenarios (*)

  1. Manually Tested

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)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Jun 29, 2019

Hi @yash7690. Thank you for your contribution
Here is 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.3-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

@magento-cicd2
Copy link
Contributor

magento-cicd2 commented Jul 1, 2019

CLA assistant check
All committers have signed the CLA.

@yash7690
Copy link
Author

yash7690 commented Jul 3, 2019

@magento-cicd2 , This commit shows me error of sematic version failure and asks me to update minor version of module. But the confusion is, the widget module does not have version in either composer.json or module.xml, so how can i solve this error ?

@yash7690
Copy link
Author

@magento-engcom-team Please let me know solution for my query.

* @param \Magento\Framework\DataObject $parameter
* @return string
*/
protected function getCssClasses($parameter)
Copy link
Contributor

Choose a reason for hiding this comment

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

Please, make method private and SVC build failures will be resolved

Copy link
Author

Choose a reason for hiding this comment

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

I have made the changes suggested by you, but still it shows build failed. This time, it is showing that array_merge is being used in a forloop, which is right but actually it is not my change, default extension is having the same code. Can you please advice here what can be done ?

@ghost ghost assigned sidolov Aug 15, 2019
@ghost ghost added the Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround. label May 11, 2020
VladimirZaets
VladimirZaets previously approved these changes Jul 28, 2020
@magento-engcom-team
Copy link
Contributor

Hi @VladimirZaets, thank you for the review.
ENGCOM-7905 has been created to process this Pull Request
✳️ @VladimirZaets, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

Copy link
Contributor

@engcom-Alfa engcom-Alfa left a comment

Choose a reason for hiding this comment

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

Hi @yash7690 . We have some problems with checkout to your branch. Could you update it?

@ghost ghost dismissed VladimirZaets’s stale review July 30, 2020 11:18

Pull Request state was updated. Re-review required.

@VladimirZaets
Copy link
Contributor

@magento run all tests

@engcom-Dash
Copy link
Contributor

Hello @yash7690,

Thanks for your contributions!

Please resolve the conflict so we can proceed with this PR.

Thanks!

@engcom-Dash
Copy link
Contributor

Closing this PR since it has not been updated in a while. Please feel free to reopen if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Lib/Frontend Component: CatalogWidget Component: Widget Partner: Krish TechnoLabs partners-contribution Pull Request is created by Magento Partner Priority: P3 May be fixed according to the position in the backlog. Release Line: 2.4 Severity: S3 Affects non-critical data or functionality and does not force users to employ a workaround.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Usage of non-numeric value for "Number of Products to Display" setting in "Catalog Products List" widget leads to an exception
10 participants