Currently, the ReverseTopicMappingService will bypass any IAssociatedTopicBindingModel instances whose UniqueKey is null or empty. But if a UniqueKey is empty, that should be used to delete any existing topic references that have the same Key. That's how attributes work in the ReverseTopicMappingService*, but not topic references. This isn't necessarily a bug, but it's definitely an unintuitive and unnecessary limitation that should be resolved.
The relevant code is within the SetReference() method of the ReverseTopicMappingService.
* At least assuming the attribute isn’t backed by a property which requires enforcement of business logic (#65).
Currently, the
ReverseTopicMappingServicewill bypass anyIAssociatedTopicBindingModelinstances whoseUniqueKeyisnullorempty. But if aUniqueKeyis empty, that should be used to delete any existing topic references that have the sameKey. That's how attributes work in theReverseTopicMappingService*, but not topic references. This isn't necessarily a bug, but it's definitely an unintuitive and unnecessary limitation that should be resolved.The relevant code is within the
SetReference()method of theReverseTopicMappingService.* At least assuming the attribute isn’t backed by a property which requires enforcement of business logic (#65).