-
Notifications
You must be signed in to change notification settings - Fork 293
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
Change regex of BRZipCodeField #177
Conversation
Please remove the .po/.mo changes from the patches. Those are handled separately through Transifex. |
Ok |
I'm change the regex to supporte many types of numbers: - 71000-000 - 71.000-000 - 71000-000
Removed |
Now, need access the django-localflavor in Transifex. I'm send a request to come in. |
@claudep files removed |
I'll let @avelino do the merge. |
Why validate point in CEP (zipcode of Brazil)? |
Yes, the point in zipcode is not default to use. I go remove this. |
@gilsondev I think this solution is bad, if a user puts a "," for example would break their implementation. |
So, you think better not change the pattern? |
Thinking about the use of lib, with this implementation not worth, if it is a generic implementation Yes. |
I thought it would be interesting to have more than one format for zipcode |
I'm change the regex to support many types of numbers: