How oktaliem/creditcardconverter works
Project type and purpose
• This is a small, standalone Java library/CLI tool whose sole responsibility is to mask credit-card numbers according to various patterns.
• It uses Maven for build, JUnit (4.12) for testing, and has a single entry point: CreditCardMaskApplication.
File structure
• Top-level:
• pom.xml — Maven build, dependency, and plugin configuration
• README.md — project description and sample test logs
• src/main/java/com/test/application
• CreditCardMaskApplication.java — main application logic (parses input, delegates to masking service)
• src/test/java/com/test/application/test
• CreditCardMaskTest.java — JUnit test cases covering input variations and expected outputs
Key components
a. CreditCardMaskApplication (CLI or Library API)
b. MaskingService (core business logic)
c. MaskStrategy or PatternHandlers (encapsulate various masking formats)
d. Input Parser / Validator (ensures non-empty number, valid mask parameter)
e. Output Generator (formats result or error messages)
f. Test Suite (JUnit harness)
g. Maven Build & Dependency Manager (pom.xml)
Relationships and data-flow
• Input enters via the Application layer (CLI args or API call)
• Application invokes Input Parser → Validation
• Valid data passed to MaskingService
• MaskingService selects appropriate MaskStrategy (e.g., star-mask, block-mask)
• MaskStrategy returns masked string
• Application routes result to Output Generator → STDOUT/Error code
• JUnit Test Suite invokes MaskingService directly and asserts results
• Maven orchestrates compile → test → package phases
Architectural patterns and principles
• Single Responsibility: each strategy handles one masking pattern
• Strategy Pattern: interchangeable masking algorithms passed to the service
• Layered approach:
• Presentation (CLI/API)
• Application (orchestration)
• Domain (masking logic)
• Infrastructure (Maven, JUnit)