How vladislavfurdak/blazornexus works
Main Components
a) Core Navigation Module:
• INavigationManager<T> interface as the primary interaction point
• To the PathMapper and RouteMapper components
b) Storage Layer:
• SessionStorageRepository for maintaining navigation state
• To the core navigation module
c) URI Handling Layer:
• PathMapper and RouteMapper components
• Connection to UriUtils for URI manipulation
d) Integration Layer:
• DependencyInjection module
• Connection points to host Blazor applications
[Host Blazor Application]
• ↑
[DependencyInjection Module]
• ↑
• Navigation |
• Manager |←--------[Session Storage]
• ↑
[PathMapper] [RouteMapper]
• ↓
• [URI Utils]
Key Elements to Highlight
a) Public Interface Layer:
• INavigationManager<T>
• NavigationManagerExt
• NexusNavigationOptions
b) Implementation Details:
• Relationship between Routes enum and actual Blazor pages
• Back navigation capability
• Query string parameter handling
Integration Points
• How the library integrates with Blazor's built-in NavigationManager
• Dependency injection setup
• Connection points for unit testing
Query string parameter management
Remember to include a small example showing the transformation from enum-based routing to actual URI paths, as this is a key feature of the library.