How zakabouj/addressvalidator works
Project type and purpose
• AddressValidator is a .NET 9.0 console application demonstrating address validation via Azure Maps and Entra ID.
• It follows a clean, modular, layered architecture with clear separation between UI, Service, and Data layers.
File structure
• Top-level project: AddressValidator.Console (main app) and AddressValidator.Test (test suite).
• Subfolders under AddressValidator.Console:
• Config (AzureMapsConfig)
• Models (AddressInput, AddressSearchResponse, etc.)
• Services (AddressValidationService, AzureMapsService, AzureMapsTokenService)
• Repositories (IAddressValidationRepository, JsonAddressValidationRepository)
• UI (AddressFormUI, ConsoleUIService, ValidationHistoryUI)
• Program.cs as the entry point
• Configuration: appsettings.json for Azure credentials (excluded from source control).
• CI/CD via GitHub Actions in .github/workflows.
README insights
• Emphasis on layered design, TDD, Spectre.Console UI, JSON persistence, Azure Maps API, and Entra ID.
Detailed capture of essential elements
• Test project (AddressValidator.Test) off to the side if desired, showing its unit and integration test suites targeting each layer.
• Confidence threshold configuration (80%) as part of service logic.
• Sample JSON storage file path under the repository component.