(full) Web Assembly support about google_maps HOT 3 CLOSED

Just a quick note that I've implemented this change. Sounds like Google Maps Platform API's will have to include CORS headers if they want WASM clients to connect.

from google_maps.

Never thought of this situation! Later today I will see about issuing an update where:

• Google Maps client will come with all of the Reqwest fixins' by default.
• If a crate turns off Google Maps default-features all desired features must be manually added, even for reqwest.

There is also another option:

use google_maps::prelude::*;

let google_maps_client = ClientSettings::new("YOUR_GOOGLE_API_KEY_HERE");

// Get query string from builder pattern:
let query_string = google_maps_client.time_zone(
     LatLng::try_from(dec!(50.090_903), dec!(14.400_512))?,
     Utc::now()
).query_string();

// Insert your favourite HTTP client here:
let json = reqwest::get(
    // query_string.0 = "https://maps.googleapis.com/maps/api/timezone/json?"
    query_string.0 + &query_string.1
).await?.text().await?;

// Parse JSON string into a TimeZoneResponse structure:
let time_zone: TimeZoneResponse = json.parse()?;

// Dump entire response:
println!("{:#?}", time_zone);

Putting the API key in the client is not necessarily bad practice! Just restrict the key to the necessary API's, and make sure you put quotas you're comfortable with - so you don't get a huge bill. https://console.cloud.google.com/google/maps-apis/quotas

from google_maps.

It looks like this approach isn't the best after all.

See, the Google Maps API this is using seems to be designed for servers first. Trying to access it via fetch simply leads to CORS getting in the way (the servers don't include CORS headers, and getting opaque responses is useless).

The correct way to use Maps API client side, for now at least, is via Google Maps JavaScript API + Rust bindings via wasm_bindgen (which do not seem to exist as a crate at the moment).
... or write a server proxying the requests in Rust, and call that instead.

In light of Google's inherent limitations, i consider this issue as irrelevant to this crate. Sorry for bothering.

from google_maps.