You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The bundle assumes that each postal code is unique for a country and maps to one location (latitude + longitude), which is not exactly the case in the real world. When importing data the same postal code may appear several times for slightly different locations and with different names. So I don't think it's a good idea trying so save the name as well.
I'm thinking about a location search where you choose your country and then type a postal code or city name.
This could then easily be achieved by using your bundles table which adds a great feature, don't you think?
But i get you point too. So for this use case you recommend overriding the addEntries method for the fixtures and extend your existing GeoPostalCode Entity?
I think the
city
resp.location
name for apostalCode
can be very useful.I can make a PR for this as soon I am available if you like @craue .
The text was updated successfully, but these errors were encountered: