This makes a few changes to the upcoming attribute operations API. Replace and ReplaceStr now have a different behavior, in that they do not set the value unless the attribute already exists (as in, is present in the receiving object, regardless of being empty or not). Set and SetStr should be used when the intent is to define the attribute regardless of whether it exists yet.
This makes a few changes to the upcoming attribute operations API.
ReplaceandReplaceStrnow have a different behavior, in that they do not set the value unless the attribute already exists (as in, is present in the receiving object, regardless of being empty or not).SetandSetStrshould be used when the intent is to define the attribute regardless of whether it exists yet.