Import-DbaCsv - Smart Type Detection & Column Optimization (#10036)

Author: potatoqualitee

.github/dbatools-library-version.json

@@ -1,4 +1,4 @@
 {
-  "version": "2025.11.29-preview-new-20251129132142",
-  "notes": "Version of dbatools.library to use for CI/CD and development."
+  "version": "2025.12.4-preview-csvvvvvv-20251204203741",
+  "notes": "Version of dbatools.library to use for CI/CD and development"
 }

CLAUDE.md

@@ -966,6 +966,31 @@ Don't add excessive tests, but don't skip tests either. When making changes:
 - Creating a new command? Add parameter validation and 1-3 integration tests
 - Refactoring without behavior changes? Existing tests may be sufficient
 
+### Local Testing Setup
+
+To test commands locally during development:
+
+```powershell
+# 1. Import the module directly from the psm1 file
+Import-Module .\dbatools.psm1
+# 1a. ONLY IF any errors about dbatools.library
+Import-Module C:\gallery\dbatools.library
+
+# 2. Get the test configuration (private command)
+$TestConfig = Get-TestConfig
+
+# 3. Now you can use $TestConfig properties in your tests
+$TestConfig.instance1    # First test SQL instance
+$TestConfig.instance2    # Second test SQL instance
+$TestConfig.instance3    # Third test SQL instance
+$TestConfig.SqlCred      # Test credentials, all connections need this
+$TestConfig.Temp         # Temp directory for test files
+# 4. Set the default paras for sqlcred
+$PSDefaultParameterValues["*:SqlCredential"] = $TestCofig.SqlCred
+```
+
+This allows you to manually test commands against actual SQL Server instances before running the full test suite.
+
 ## VERIFICATION CHECKLIST
 
 **Comment and Parameter Preservation:**