-
-
Notifications
You must be signed in to change notification settings - Fork 943
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
fix(location): update valid ZIP ranges for FL and VA #3167
Conversation
✅ Deploy Preview for fakerjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## next #3167 +/- ##
=======================================
Coverage 99.97% 99.97%
=======================================
Files 2798 2798
Lines 227793 227793
Branches 959 957 -2
=======================================
+ Hits 227726 227732 +6
+ Misses 67 61 -6
|
FL and VA don't throw any errors anymore, but what about these: Mismatch detected: Generated 72643 for AR but located in MO
Mismatch detected: Generated 83414 for ID but located in WY
Mismatch detected: Generated 96799 for HI but located in AS |
see #3169 these seem to be various one-off weirdnesses, can probably address later |
fix #3165
Changes the VA zips to 22201-24599 (this is not every VA code, but shouldnt overlap with DC)
Changes the FL zips to
"320","321","322","323","324","325","326","327","328","329","330","331","332","333","334","335","336","337","338","339","341","342","344","346","347","349"
plus a 2 digit endingNot very elegant, but this ensures we don't generate 340... military ZIPs.
ref https://en.wikipedia.org/wiki/List_of_ZIP_Code_prefixes