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
When we do this, we could remove the proxy classes for Microsoft.Spatial and instead use adapters to create GeoJson types. This would not only reduce the amount of code to maintain, but also remove the intentional duplication in SpatialFormatter to improve perf (no reason to allocate extra).
The proxies for Microsoft.Spatial still exist but the comment implies the intention was to remove them. That's not what we actually want to do, though, right? So we can still support Microsoft.Spatial types? Maybe the comment is just misleading.
Once the Azure Core change (#10592) is merged, we need to re-enabled the APIs in Search to support it.
The text was updated successfully, but these errors were encountered: