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
Is there any particular reason why you return only the string value of photo attributions in metadata instead of the full link? Because according to Google Places rules, we are supposed to include a tappable link to those attributions when presenting the image.
Also, is there any particular reason why image is returned as an Image widget instead of directly as a Uint8List? If is was possible to get the raw image data, we could do something else with it, store it somewhere (but maybe that's against the ToS, I don't know), or build our own memory image with custom parameters (especially for fit).
The text was updated successfully, but these errors were encountered:
Is there any particular reason why you return only the string value of photo attributions in metadata instead of the full link? Because according to Google Places rules, we are supposed to include a tappable link to those attributions when presenting the image.
We actually return both, or rather only one - the one that we get back.
On the web we get back url so we return it.
On android for example we get back a Bitmap, so we can't return an actual url - see Response
We also return the attribution as field, so you should be able to use that to get the full image url; no?
Also, is there any particular reason why image is returned as an Image widget instead of directly as a Uint8List? If is was possible to get the raw image data, we could do something else with it, store it somewhere (but maybe that's against the ToS, I don't know), or build our own memory image with custom parameters (especially for fit).
We can probably return that as Uint8List, make sense.
Is there any particular reason why you return only the string value of photo attributions in metadata instead of the full link? Because according to Google Places rules, we are supposed to include a tappable link to those attributions when presenting the image.
Also, is there any particular reason why image is returned as an
Image
widget instead of directly as a Uint8List? If is was possible to get the raw image data, we could do something else with it, store it somewhere (but maybe that's against the ToS, I don't know), or build our own memory image with custom parameters (especially for fit).The text was updated successfully, but these errors were encountered: