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 suggest we make it absolutely clear that the APIs of DynamicObj/DynObj handles dynamic properties, and should therefore reflect that in the naming of methods.
Examples:
//Current API stateleta= DynamicObj()
a.SetValue("some prop",42)
a.GetValue("some prop")
a |> DynObj.tryGetTypedValue<int>"some prop"
a |> DynObj.remove "some prop"
//Proposed naming changesleta= DynamicObj()
a.SetProperty("some prop",42)
a.GetPropertyValue("some prop")
a |> DynObj.tryGetTypedPropertyValue<int>"some prop"
a |> DynObj.removeProperty "some prop"
I suggest we make it absolutely clear that the APIs of
DynamicObj/DynObj
handles dynamic properties, and should therefore reflect that in the naming of methods.Examples:
cc @HLWeil
The text was updated successfully, but these errors were encountered: