 lilleman
|
71b17d104b
|
Answer architecture round 1: fence keeps a locality holding both a street and a postal code, returns what it dropped so the SE import still exits on a lost kommun and the US one counts its counties, and file item 168 for data-import tests
|
2026-10-09 12:35:12 +02:00 |
|
|
lilleman
|
6d285249e4
|
Meet the parent-has-a-child fence in one shared geo.fence step, which states the locality row each country hands it
|
2026-10-09 12:35:12 +02:00 |
|
|
lilleman
|
ad599675d1
|
Answer prose round 2: top_streets says what it returns, and CheckIdentifier's doc opens with what it does
|
2026-10-07 02:27:24 +02:00 |
|
|
lilleman
|
c2147d2282
|
Answer prose round 1 and product-owner round 1: CheckIdentifier's doc counts a bound name, FuncCall and the grammar doc say PathRead and identifiers, the Layout's list.go, name.go and data-import rows read on one pass, the locality row says a postort with no street is dropped, geo.py's docs name what they take, well_cased says what it drops, and item 61 names the next steps to share
|
2026-10-07 02:27:24 +02:00 |
|
|
lilleman
|
2431edeab0
|
Answer stability round 1: README's pick.go and datatype.go rows name what stayed, geo.py's options sort with each script's own, geo.py claims only shared steps, route defines fromRow as pathPos does, and disagreement's panic names the kinds
|
2026-10-07 02:27:24 +02:00 |
|
|
lilleman
|
ae5b95e88a
|
Share the steps every country's geo import takes in geo.py, so geo-se.py and geo-us.py hold only their own rules
|
2026-10-07 02:27:24 +02:00 |
|