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
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
The $featureProperties expression variable should be renamed $featureAttributes to match the MGLFeature.attributes property. The iOS/macOS map SDK avoids using the term “property” to refer to things that aren’t represented by class or instance properties in Objective-C or Swift.
If this change doesn’t take place before the iOS map SDK v4.0.0 release, we can support both variable names but prefer $featureAttributes. ($featurePropertiesisn’t documented, in any case.) The NSExpression.featurePropertiesVariableExpression property would ideally be renamed as well; we’d have to leave a deprecated alias in place for it.
The
$featureProperties
expression variable should be renamed$featureAttributes
to match theMGLFeature.attributes
property. The iOS/macOS map SDK avoids using the term “property” to refer to things that aren’t represented by class or instance properties in Objective-C or Swift.If this change doesn’t take place before the iOS map SDK v4.0.0 release, we can support both variable names but prefer
$featureAttributes
. ($featureProperties
isn’t documented, in any case.) TheNSExpression.featurePropertiesVariableExpression
property would ideally be renamed as well; we’d have to leave a deprecated alias in place for it./cc @fabian-guerra
The text was updated successfully, but these errors were encountered: