We are using featureReduction to display clusters of records that are close together and provide a label on the cluster itself. When the clusters are too close together, some clusters are not labeled. Since setting the deconflictionStrategy to none completly removes them from collision detection, the behavior we saw in 4.18 was not intended. Any way to submit a request to get it to function as in 4.18? Any timeline when the 4.20/4.21 ordering of collisions bug would get fixed?
... View more
I'm running into an issue with deconflictionStrategy not working as expected for FeatureLayers that use collection source for their data instead of a url. At version 4.18, when I set the deconflictionStrategy to 'none', needed for FeatureReduction, on FeatureLayers from a collection, labels for layers that were below that layer were removed so they didn't overlap. Other layers in the map have the default deconflictionStrategy of 'static'. At 4.19 and above, the labels are now covering this feature layer. Below codepens are the same except for the version number Codepen for 4.18, where it was working as expected: https://codepen.io/alexurq/pen/JjJwGEX Codepen for 4.19 where it isn't: https://codepen.io/alexurq/pen/OJgrMbQ Is there any addtional property that needs to be set prevent the overlaping of the labels?
... View more