Add Get-ClassTypeNameFromDataFile function and update documentation links (#2979)

This pull request primarily enhances how documentation URLs are
generated in the `Get-DiscussionId.ps1` script by including the class
type name in the URL path. It introduces a new function to extract the
class type name from data files and updates all relevant code paths to
use this value. Additionally, a minor metadata update is made to a
documentation markdown file.

**Improvements to documentation URL generation:**

* Added a new function `Get-ClassTypeNameFromDataFile` to extract the
`typeName` property from YAML data files, with error handling for
missing or invalid files. (.powershell/docs/Get-DiscussionId.ps1)
* Updated all references to data file paths to use the correct
directory: `.\docs\data\classesThis pull request primarily enhances how
documentation URLs are generated in the `Get-DiscussionId.ps1` script by
including the class type name in the URL path. It introduces a new
function to extract the class type name from data files and updates all
relevant code paths to use this value. Additionally, a minor metadata
update is made to a documentation markdown file.

**Improvements to documentation URL generation:**

* Added a new function `Get-ClassTypeNameFromDataFile` to extract the
`typeName` property from YAML data files, with error handling for
missing or invalid files. (.powershell/docs/Get-DiscussionId.ps1)
instead of `.\docsThis pull request primarily enhances how documentation
URLs are generated in the `Get-DiscussionId.ps1` script by including the
class type name in the URL path. It introduces a new function to extract
the class type name from data files and updates all relevant code paths
to use this value. Additionally, a minor metadata update is made to a
documentation markdown file.

**Improvements to documentation URL generation:**

* Added a new function `Get-ClassTypeNameFromDataFile` to extract the
`typeName` property from YAML data files, with error handling for
missing or invalid files. (.powershell/docs/Get-DiscussionId.ps1)
. (.powershell/docs/Get-DiscussionId.ps1)
[[1]](diffhunk://#diff-a57e4bef6b3d02f906acbc6ae2295862ef115ce58be8845e0d635d9d31e6d346R482-R486)
[[2]](diffhunk://#diff-a57e4bef6b3d02f906acbc6ae2295862ef115ce58be8845e0d635d9d31e6d346R767-R772)
* Modified the construction of documentation URLs to include the class
type name as a path segment, ensuring URLs are more specific and
organized. (.powershell/docs/Get-DiscussionId.ps1)
[[1]](diffhunk://#diff-a57e4bef6b3d02f906acbc6ae2295862ef115ce58be8845e0d635d9d31e6d346L493-R517)
[[2]](diffhunk://#diff-a57e4bef6b3d02f906acbc6ae2295862ef115ce58be8845e0d635d9d31e6d346L538-R562)
[[3]](diffhunk://#diff-a57e4bef6b3d02f906acbc6ae2295862ef115ce58be8845e0d635d9d31e6d346L755-R781)
* Ensured that the class type name is consistently extracted and used in
both the main discussion creation logic and in the loop over markdown
objects, including normalization to lowercase where appropriate.
(.powershell/docs/Get-DiscussionId.ps1)

**Documentation metadata update:**

* Added a `discussionId` field to the front matter of
`docs/content/docs/get-started/validation/index.md`.

Author: MrHinsh

.powershell/docs/Get-DiscussionId.ps1

@@ -418,6 +418,28 @@ function Get-ClassNameFromDataFile {
     }
 }
 
+# Function to get class name from data file
+function Get-ClassTypeNameFromDataFile {
+    param(
+        [string]$DataFilePath
+    )
+    
+    if (-not (Test-Path $DataFilePath)) {
+        Write-WarningLog "Data file not found: $DataFilePath"
+        return $null
+    }
+    
+    try {
+        $yamlContent = Get-Content -Path $DataFilePath -Raw
+        $data = ConvertFrom-Yaml -Yaml $yamlContent
+        return $data.typeName
+    }
+    catch {
+        Write-WarningLog "Failed to parse data file $DataFilePath : $($_.Exception.Message)"
+        return $null
+    }
+}
+
 # Function to convert class name to friendly name
 function Convert-ClassNameToFriendlyName {
     param(
@@ -457,9 +479,11 @@ function Find-OrCreateDiscussion {
 
     # Get class name from data file if available
     $className = $null
+    $classTypeName = "unknown"
     if ($dataFile) {
-        $dataFilePath = Join-Path ".\docs\" $dataFile
+        $dataFilePath = Join-Path ".\docs\data\classes\" $dataFile
         $className = Get-ClassNameFromDataFile -DataFilePath $dataFilePath
+        $classTypeName = Get-ClassTypeNameFromDataFile -DataFilePath $dataFilePath
     }
 
     # Convert class name to friendly name
@@ -490,7 +514,7 @@ function Find-OrCreateDiscussion {
                 # Generate updated discussion body to ensure consistency
                 $docUrl = ""
                 if ($hugoMarkdown.FrontMatter.slug) {
-                    $docUrl = "https://devopsmigration.io/docs/reference/$($hugoMarkdown.FrontMatter.slug)/"
+                    $docUrl = "https://devopsmigration.io/docs/reference/$classTypeName/$($hugoMarkdown.FrontMatter.slug)/"
                 }
                 elseif ($hugoMarkdown.ReferencePath) {
                     $relativePath = $hugoMarkdown.ReferencePath.Replace('docs/', '').Replace('\', '/')
@@ -535,7 +559,7 @@ function Find-OrCreateDiscussion {
         # Generate documentation URL
         $docUrl = ""
         if ($hugoMarkdown.FrontMatter.slug) {
-            $docUrl = "https://devopsmigration.io/docs/reference/$($hugoMarkdown.FrontMatter.slug)/"
+            $docUrl = "https://devopsmigration.io/docs/reference/$classTypeName/$($hugoMarkdown.FrontMatter.slug)/"
         }
         elseif ($hugoMarkdown.ReferencePath) {
             $relativePath = $hugoMarkdown.ReferencePath.Replace('docs/', '').Replace('\', '/')
@@ -740,10 +764,12 @@ foreach ($hugoMarkdown in $hugoMarkdownObjects) {
             if ($existingDiscussion) {
                 # Get class name from data file if available
                 $className = $null
+                $classTypeName = "unknown"
                 $dataFile = $hugoMarkdown.FrontMatter.dataFile
                 if ($dataFile) {
-                    $dataFilePath = Join-Path ".\docs\" $dataFile
+                    $dataFilePath = Join-Path ".\docs\data\classes\" $dataFile
                     $className = Get-ClassNameFromDataFile -DataFilePath $dataFilePath
+                    $classTypeName = (Get-ClassTypeNameFromDataFile -DataFilePath $dataFilePath).ToLower()
                 }
 
                 # Convert class name to friendly name
@@ -752,7 +778,7 @@ foreach ($hugoMarkdown in $hugoMarkdownObjects) {
                 # Generate documentation URL
                 $docUrl = ""
                 if ($hugoMarkdown.FrontMatter.slug) {
-                    $docUrl = "https://devopsmigration.io/docs/reference/$($hugoMarkdown.FrontMatter.slug)/"
+                    $docUrl = "https://devopsmigration.io/docs/reference/$classTypeName/$($hugoMarkdown.FrontMatter.slug)/"
                 }
                 elseif ($hugoMarkdown.ReferencePath) {
                     $relativePath = $hugoMarkdown.ReferencePath.Replace('\', '/')

docs/content/docs/get-started/validation/index.md

@@ -1,14 +1,14 @@
 ---
-title: "Validating your Azure DevOps Migration Tools migration"
+title: Validating your Azure DevOps Migration Tools migration
 description: This tutorial covers the steps to validate and verify your migration using the Azure DevOps Migration Tools.
 short_title: Get Validated
 weight: 10
 aliases:
-  - /validation/
+- /validation/
 date: 2025-09-01T09:00:00Z
+discussionId: 2978
 
 ---
-
 The Azure DevOps Migration Tools use a two-step validation process to ensure a smooth and successful migration. This process helps catch configuration or data issues early, saving time and preventing unnecessary data loading when migration cannot proceed.
 
 ## 1. Pre-Data-Load Validation
@@ -36,4 +36,4 @@ By running validation both before and after data loading, the migration process
 
 For more details on each validator, see their dedicated documentation pages:
 - [`TfsWorkItemTypeValidatorTool`]({{< ref "/docs/reference/tools/tfsworkitemtypevalidatortool/" >}})
-- [`TfsValidateRequiredFieldTool`]({{< ref "/docs/reference/tools/tfsvalidaterequiredfieldtool/" >}})
+- [`TfsValidateRequiredFieldTool`]({{< ref "/docs/reference/tools/tfsvalidaterequiredfieldtool/" >}})