How noelmugnier/fhydia works
Main Components
a) Core Library Components (Central Focus):
• Configuration System
• Builders System
• Enrichment Pipeline
• Formatters System
• Filters System
b) Integration Points:
• ASP.NET Core Integration
• Client Application Integration
Top Layer (Client Integration)
• Configuration points (TypeConfiguration)
• Controller integration
Middle Layer (Core Processing)
• Divide into sub-components:
• Builder System (Left side)
• Enrichment Pipeline (Center)
• Formatters (Right side)
Bottom Layer (Runtime Processing)
• Endpoint Filters
• Response Transformation
• Format-Specific Output
Detailed Component Breakdown
Core Components (Show as interconnected modules):
┌─ Configuration System ─┐ ┌─ Builder System ─┐
• TypeConfiguration │───▶│ - FhydiaBuilder │
• HyperMediaConfig │ │ - LinkBuilder │
• ┘ └─────────────────┘
• ▼
┌─ Enrichment Pipeline ─┐ ┌─ Formatters ─┐
• ObjectEnricher │───▶│ - HAL │
• LinkInjection │ │ - (Others) │
• ┘ └─────────────┘
Implementation Details
Implementation aspects:
• EndpointFilter integration
• ExpandoObject transformation
• Accept header handling
• Formatter selection
The minimal impact on existing code
Keep the focus on the library's core purpose: enriching endpoint responses with HATEOAS features while maintaining a clean separation between configuration and runtime behavior.
Remember to include future planned components (like additional formatters) in a different shade or pattern to indicate their planned status.