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
I've currently used excludeFields to just exclude the geometries from the query, so I've found a workaround, but figured I would take note of the issue here.
Integrating the postgis stuff, everything works well except
GeometryCollection
, which apparently has a nested propertyFor a given property
bounds
, the admin is generating this query:but the
geometries
is actually another nested object and the correct format should beHere is my config
I've currently used
excludeFields
to just exclude thegeometries
from the query, so I've found a workaround, but figured I would take note of the issue here.Temporary fix:
The text was updated successfully, but these errors were encountered: