Renamed TranslateTopicPointers to TranslateLegacyTopicReferences

The terminology for "topic pointers" was standardized as "topic references"—and what the `ExportOptions` refers to as `TopicPointers` are no longer the preferred method of modeling topic references. To help unify the vocabulary, while simultaneously clarifying that this is for legacy support, I've renamed this option to `TranslateLegacyTopicReferences`.

Author: JeremyCaney

OnTopic.Data.Transfer/Interchange/ExportOptions.cs

@@ -3,6 +3,7 @@
 | Client        Ignia, LLC
 | Project       Topics Library
 \=============================================================================================================================*/
+using System;
 using System.Diagnostics.CodeAnalysis;
 
 namespace OnTopic.Data.Transfer.Interchange {
@@ -96,10 +97,10 @@ public bool IncludeNestedTopics {
     public bool IncludeChildTopics { get; set; }
 
     /*==========================================================================================================================
-    | TRANSLATE TOPIC POINTERS
+    | TRANSLATE LEGACY TOPIC REFERENCES
     \-------------------------------------------------------------------------------------------------------------------------*/
     /// <summary>
-    ///   Determines whether attributes that appear to be topic pointers should be mapped to their fully qualified unique key.
+    ///   Determines whether attributes that appear to be topic reference should be mapped to its fully qualified unique key.
     /// </summary>
     /// <remarks>
     ///   <para>
@@ -129,6 +130,9 @@ public bool IncludeNestedTopics {
     ///     enabled when it's known to be necessary to maintain backward compatibility.
     ///   </para>
     /// </remarks>
+    public bool TranslateLegacyTopicReferences { get; set; }
+
+    [Obsolete("The TranslateTopicPointers option has been renamed to TranslateLegacyTopicReferences", true)]
     public bool TranslateTopicPointers { get; set; }
 
   } //Class

OnTopic.Data.Transfer/Interchange/TopicExtensions.cs

@@ -163,7 +163,7 @@ childTopic.ContentType is "List"
       | Get attribute value
       \-----------------------------------------------------------------------------------------------------------------------*/
       string? getAttributeValue(AttributeRecord attribute) =>
-        options.TranslateTopicPointers && attribute.Key.EndsWith("ID", StringComparison.InvariantCultureIgnoreCase)?
+        options.TranslateLegacyTopicReferences && attribute.Key.EndsWith("ID", StringComparison.InvariantCultureIgnoreCase)?
           GetUniqueKey(topic, attribute.Value, options) :
           attribute.Value;
 
@@ -465,9 +465,9 @@ bool useCustomMergeRules(AttributeData attribute) =>
     /// </summary>
     /// <remarks>
     ///   Note that this function is <i>exclusively</i> required for maintaining backward compatibility the <see cref="
-    ///   ExportOptions.TranslateTopicPointers"/> option/ With the release of OnTopic 5.0.0, and OnTopic Data Transfer 3.0.0,
-    ///   implementers should prefer the use of <see cref="Topic.References"/>. The <see cref="GetUniqueKey(Topic, String?,
-    ///   ExportOptions)"/> method continues to be included primarily for backward compatibility with legacy database
+    ///   ExportOptions.TranslateLegacyTopicReferences"/> option/ With the release of OnTopic 5.0.0, and OnTopic Data Transfer
+    ///   3.0.0, implementers should prefer the use of <see cref="Topic.References"/>. The <see cref="GetUniqueKey(Topic,
+    ///   String?, ExportOptions)"/> method continues to be included primarily for backward compatibility with legacy database
     ///   configurations.
     /// </remarks>
     /// <param name="topic">The source <see cref="Topic"/> to operate off of.</param>