27027 added date format adjustment for 'validate-dob' rule

[sergiy-v]

Description

Added date format adjustment for 'validate-dob' rule

Fixed Issues

#27027

Manual testing scenarios

See issue description from #27027.

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]

Hi @sergiy-v. 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.4-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Guide documentation.

[magento-engcom-team]

Hi @rogyar, thank you for the review.
ENGCOM-7036 has been created to process this Pull Request

[engcom-Bravo]

✔️ QA Passed

No error appears after switching to the PR

[m2-assistant]

Hi @sergiy-v, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

[nelero]

Thanks
how to use it with cweagans/composer-patches ? like in this message #26675 (comment)
is there anything to remove in paths of diff file ?

Thanks

[sergiy-v]

Thanks
how to use it with cweagans/composer-patches ? like in this message #26675 (comment)
is there anything to remove in paths of diff file ?

Thanks

Hello @nelero,
Not sure I 100% understand what are you looking for.
According to instruction for patch applying from your comment you are looking for PR diff, you can get by the following link.
https://github.com/magento/magento2/pull/27149.diff

Thank you.

[nelero]

hi @sergiy-v ,
thanks for the link. My question was if there was anything to remove in the paths of the content of the diff file. If you have a look at the #26675 (comment) (the comment pointed), you'll see that we have to remove some parts of the paths written in the diff file in order to apply it correctly.
So i was wondering if we had to do the same with this diff file.
Thanks

[nelero]

hi @sergiy-v , i found my way to apply this patch with cweagans/composer-patches

1. Create the patches/composer folder at the magento root directory
2. copy first part of diff file, related to magento/module-customer in a file in this folder, i.e. 27149-customer.diff
3. Copy the last part of diff file, related to magento/module-ui in another file 27149-ui.diff
4. In those 2 files, remove app/code/Magento/Customer/ and app/code/Magento/Ui/ wherever it appears
5. Add these lines in the composer.json file :

"extra": {
         "magento-force": "override",
         "composer-exit-on-patch-failure": true,
         "patches": {
             "magento/module-customer":{
                 "1.0": "patches/composer/27149-customer.diff"
             },
             "magento/module-ui":{
                 "1.0": "patches/composer/27149-ui.diff"
             }
 
         }
     } 

6. Run composer -v install
7. Run composer update --lock

[sergiy-v]

hi @sergiy-v , i found my way to apply this patch with cweagans/composer-patches

Hello @nelero, nice to hear that, thank you for your update!

[matthewhaworth]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @matthewhaworth. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @matthewhaworth, here is your Magento instance.
Admin access: https://i-27149-2-4-develop.instances.magento-community.engineering/admin_4b80
Login: f55d572f Password: 65e79e93e371
Instance will be terminated in up to 3 hours.