In theory this should be easy; in practice it's less so; for tedious historical reasons we have two 'Persistable' marker objects, Persistable::Marker and Marker::MarkerHangar. I believe that the search uses the former; and guess where the functional/stats info is stored? A proper solution would merge these objects (up until now the work required to do so hasn't been justified by any gains), but it's possible to implement a hacky solution where a Marker::MarkerHangar object is added as a property of the Persistable::Marker object (which is pretty grizzly).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In theory this should be easy; in practice it's less so; for tedious historical reasons we have two 'Persistable' marker objects, Persistable::Marker and Marker::MarkerHangar. I believe that the search uses the former; and guess where the functional/stats info is stored? A proper solution would merge these objects (up until now the work required to do so hasn't been justified by any gains), but it's possible to implement a hacky solution where a Marker::MarkerHangar object is added as a property of the Persistable::Marker object (which is pretty grizzly).