How uladzimirfilipchanka/noredraw works
File structure
• Top-level modules (all Gradle-based):
• noredraw-app: the command-line entrypoint, configuration, argument parsing, Docker setup
• noredraw-core: central engine (model definitions, linking, merging, processing context)
• noredraw-loader: input source code retrieval (local folder or remote Git URL)
• noredraw-providers: built-in “plugins” that parse specific filetypes (Docker, Terraform-AWS, GitHub Actions, Gradle) to produce raw resources
• noredraw-custom-example: shows how to add your own Provider (custom extension)
• Key patterns: modular plugin architecture (Provider, Exporter, LinkStrategy, MergeStrategy interfaces), dependency injection via “@Named” annotations, staged pipeline (load → provide → link → merge → export).
Key insights from the README
• CLI parameters drive source location, export format, merge/link strategies, output path
• Providers are discovered on the classpath (core + custom jars)
• Core engine applies two phases: linking (connect related resources) and merging (collapse or group similar resources)
• Highly extensible: new Provider, Exporter, MergeStrategy, LinkStrategy can be added in minutes
a. Main components to show:
• CLI Runner (AppRunner & StarterService in noredraw-app)
• Configuration/Args parser (CliArgs, converters)
• Source loader (LocalSourceCodeProvider & RemoteRepoSourceCodeProvider in noredraw-loader)
• Provider modules (noredraw-providers + any custom jars) implementing Provider interface
• Core engine (ProcessingContext, GraphService, MergingService, model classes)
• External systems: Git repository, local filesystem
b. Relationships & interactions (data flow):
1. User invokes CLI Runner → parses arguments → Configuration
2. Loader fetches code → hands over source files to each active Provider
3. Each Provider emits zero-or-more Resource/Re-lic objects
4. Core LinkingService applies LinkStrategy implementations → produces a connected ResourceGraph
5. Core MergingService applies MergeStrategy implementations → produces final Graph model
c. Architectural patterns / design principles:
• Pipeline / staged processing
• Strategy pattern (LinkStrategy, MergeStrategy, Provider, Exporter)
• Dependency injection & module discovery (@Named annotation)
• Separation of concerns: CLI, loading, providing, core processing, exporting
d. Technology & frameworks:
• Java 17 (Eclipse-Temurin)
• Gradle multi-module build
• SLF4J + Logback
• Docker (Dockerfile for containerized CLI)