How walkerad03/d2-armor-filter works
Project type and purpose
• The module names (destiny_api.py, armor_cleaner.py, auth.py, controller.py, ui.py, workers.py) indicate it connects to Bungie’s Destiny API, authenticates a user, applies “armor cleaning” logic (business rules), and presents a user interface.
File structure
• Top level:
• main.py – application entrypoint
• config.ini – runtime configuration
• run.sh / run.bat – convenience scripts to start the app
• pyproject.toml – package metadata, dependencies
• src/
• assets/svg – static UI assets
• auth.py – handles authentication flows
• destiny_api.py – encapsulates HTTP calls to external Destiny service
• armor_cleaner.py – core business logic implementing “cleaning” rules
• workers.py – background/job-queue or threading utilities
• controller.py – orchestrates between UI, business logic, API, config
• ui.py – UI layer (likely using a GUI toolkit or CLI)
README for additional insights
• README is empty, so infer architecture from module names and standard patterns:
• MVC-like separation: ui.py (View), controller.py (Controller), armor_cleaner & destiny_api (Model/Services).