search

magento / magento2

Prior to making any Submission(s), you must sign an Adobe Contributor License Agreement, available here at: https://opensource.adobe.com/cla.html. All Submissions you make to Adobe Inc. and its affiliates, assigns and subsidiaries (collectively “Adobe”) are subject to the terms of the Adobe Contributor License Agreement.
http://www.magento.com
Open Software License 3.0
11.55k stars 9.32k forks source link

[Issue] Update zip_codes.xml #29984

Closed m2-assistant[bot] closed 4 years ago

m2-assistant[bot] commented 4 years ago

This issue is automatically created based on existing pull request: magento/magento2#29972: Update zip_codes.xml

Changed regex for zipcodes from Brazil. All zipcode must have 8 positions, with or without dash

Preconditions: (*)

Magento 2.4-develop Changed the regex to force 8 digits for zipcode in Brazil

Related Pull Requests

n/a

Fixed Issues (if relevant)

Didn't found issue but a lot of people asking for help in forums

Steps to reproduce: (*)

Format of zipcodes in Brazil: 99999-999 or 99999999

  1. Put any number less than 8 digits (ex: 01001) - ERROR
  2. Put a number with 8 digits, without dash (ex: 01001-001) - OK
  3. Put a number with 5 digits, a dash and more 3 digits (ex: 01001-001) - OK

Actual Result: :heavy_multiplication_x: It possible to use 5 digits ZIP code

Screenshot from 2020-09-21 16-25-31

Expected Result: :heavy_check_mark: all zip codes for Brazil must have 8 digits

2020-09-21_16-33

Questions or comments

First contribution to Magento, please let me know if I need to provide more info

Contribution checklist (*)

magento-engcom-team commented 4 years ago

:white_check_mark: Confirmed by @engcom-Alfa Thank you for verifying the issue. Based on the provided information internal tickets MC-37771 were created

Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

gabrieldagama commented 4 years ago

Hi @m2-assistant[bot]. Thank you for your report. The issue has been fixed in magento/magento2#29972 by @marcostrama in 2.4-develop branch Related commit(s):

The fix will be available with the upcoming 2.4.2 release.