You confirmed that first method of making the object is the right one and both of our techniques of making it ({{ }} around each value or {{ }} around the whole thing) work.
In my dataset they are "lat" and "lng" and I have the MapBox's Latitude field name and Longitude field name properties set to those and the map points display fine.
But the object passed to .selectPoint() ONLY works with "latitude" and "longitude". I tested this by aliasing my columns to latitude/longitude and it started working.
Thank you for pointing this out! I believe this is expected behavior. MapBox is expecting 'latitude' and 'longitude' specifically and in the UI we map those correctly no matter what you call them in your dataset -- but if you are manually filling out the parameters for that function then you need to adhere to their API.
Might I suggest a warning on the Latitude and Longitude field name properties that one should only use the standard field names wherever possible to avoid possible conflicts with the MapBox library? I would have suggested removing the properties and enforcing standard field names, but that would be a breaking change at this point so best not go that far.
Yes, the issue was sorted out by not using latitude/longitude aliases. The feature request is to have the selectPoint documentation note that it only works when lat/lon are not aliased.