Closed adamkorynta closed 1 year ago
It looks like Location.Builder is coded such that latitude and longitude are double, not Double and although the setters can take a Double they npe if that Double is null.
The error above indicates that the database must have rows with null lat/lon. Maybe this was just a bad assumption by the initial author?
Its an easy fix to change the fields from double->Double and to remove the null checks. IMO maybe 20 minutes of actual work.
Yeah, if I remember right our new standard is "dude, we need the lat/long." but there's a lot of old data.
Would it be reason to include the check on POST only?
Requiring it on POST seems valid.
This looks to be caused by the location not having a latitude or longitude defined.