google-map-marker does not work when latitude and longitude are provided by AngularJS about google-map

[ebidel]

We can cast those values to ensure they're floats.

Where are you getting selectedAddress.coordinates from? If they're numbers
it stuff work fine. Did you mean they're strings?

The maps api expects float numbers, not strings (
https://developers.google.com/maps/documentation/javascript/3.exp/reference#LatLngLiteral
).
On Sep 3, 2014 7:01 AM, "Radek Slupik" [email protected] wrote:

Given the following example:

Where selectedAddress.coordinates is {latitude: 20, longitude: 20} breaks
with an error in Google Maps API because this.latitude and this.longitude
in updatePosition
https://github.com/GoogleWebComponents/google-map/blob/master/google-map.html#L113
are strings, not numbers. It'd be very useful if the assumption that these
values are numbers were not there.

—
Reply to this email directly or view it on GitHub
#49.

[rightfold]

They are numbers in my data (selectedAddress.coordinates is {latitude: 20, longitude: 20}), but AngularJS calls setAttribute and setAttribute casts the value to a string.

[ebidel]

I'll put in a check, but when I test .setAttribute('latitude', 37.879) or .setAttribute('latitude', '37.879') directly on the map element in the console, there are no errors.

Have you seen https://github.com/matjaz/angu-poly? It's a lib that makes Angular understand two-way bindings on attributes.