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
Currently, only addresses in string form can be geocoded. It would be interesting to enable objects that can be represented as strings (with a __toString() method or by implementing the \Stringable interface) to be geocoded too.
The text was updated successfully, but these errors were encountered:
I think so, because I was referring to the GeocoderListener which only checks a property or a getter returning a string.
In my case, I store the address in an embeddable doctrine object which implements the Stringable interface. I could simply add a getAddressAsString method with the Address attribute, but having the ability to directly mark my getAddress() getter would be a nice improvement.
I'll be able to work on a PR when I've finished fighting the test failure!
Currently, only addresses in string form can be geocoded. It would be interesting to enable objects that can be represented as strings (with a
__toString()
method or by implementing the\Stringable
interface) to be geocoded too.The text was updated successfully, but these errors were encountered: