You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in performant-software/core-data-cloud#338, most projects will probably want to show points in the map search (as distinct from the single-place view) even if they're using polygonal data because showing tons of polygons on the map would be very busy.
However, some projects may still want to show polygons in the search view. Core Data Places should expose a setting in config.json to allow developers to toggle between the two modes. This setting would be forwarded to the new prop from performant-software/react-components#317.
When the setting is disabled, we should save bandwidth/performance by excluding the geometry field from the results using Typesense's exclude_fields param. For future flexibility, we should also add an item to config.json that allows the user to add more fields to the exclusion list.
The text was updated successfully, but these errors were encountered:
As mentioned in performant-software/core-data-cloud#338, most projects will probably want to show points in the map search (as distinct from the single-place view) even if they're using polygonal data because showing tons of polygons on the map would be very busy.
However, some projects may still want to show polygons in the search view. Core Data Places should expose a setting in
config.json
to allow developers to toggle between the two modes. This setting would be forwarded to the new prop from performant-software/react-components#317.When the setting is disabled, we should save bandwidth/performance by excluding the geometry field from the results using Typesense's exclude_fields param. For future flexibility, we should also add an item to config.json that allows the user to add more fields to the exclusion list.
The text was updated successfully, but these errors were encountered: