Turns out it was a bug caused by updating a service. We just chuck all the data in to update e.g. $set: req.body.data This is bad and this is an example why this was bad. Since coordinates were never set on the front end they ended up with the default 0, 0. This feature will fix this issue #111
Turns out it was a bug caused by updating a service. We just chuck all the data in to update e.g.
$set: req.body.data
This is bad and this is an example why this was bad. Since coordinates were never set on the front end they ended up with the default 0, 0. This feature will fix this issue #111