Closed sirusbaladi closed 2 weeks ago
See api docs .getGeofence(identifier) to fetch the desired geofence info.
See api docs .getGeofence(identifier) to fetch the desired geofence info.
it makes a lot of sense to add it in the object returned by onGeofence. For now, I'm adding it in the extra field of the object.
It is not inefficient to simply use .getGeofence.
I don’t plan on providing the geofence to the event.
You’re always free to add any arbitrary meta data to the geofence event via Geofence.extras
, including the geofence lat/lng. It’s what I do in the demo app.
You’re always free to add any arbitrary meta data to the geofence event via
Geofence.extras
, including the geofence lat/lng. It’s what I do in the demo app.For now, I'm adding it in the extra field of the object.
Yes that's what I've ended up doing. I think it cleaner than calling getGeofence again. Still think that should come within the geofence field in event but it works. - > event : {..., geofence {object}}
Still think that should come within the geofence field
It doesn’t matter. There are multiple ways to get the desired information required by a minority of users.
Hi,
The onGeofence event right now returns within the location field the longitude and latitude of where the user is within the geofence. It would be nice if it also returned the longitude and latitude of the geofence center itself.
Having this would make the object more complete and would help in making the code cleaner. I have some use-cases where I exactly need this.
Thanks.