How raphaeltarita/multiplaform-metadata works
[API Layer]
• ↓
[Implementation Layer]
• ↓
[Storage Layer]
Detailed Component Breakdown
a) API Layer (Top):
• [Metadata] ← [TypedMetadata<T>]
• [NullableMetadata] ← [NullableTypedMetadata<T>]
• MetadataDelegate interface connecting to these core interfaces
b) Implementation Layer (Middle):
• [StandardMetadataImpl]
• [StandardTypedMetadataImpl]
• [StandardNullableMetadataImpl]
• [StandardNullableTypedMetadataImpl]
• [MetadataDelegateImpl]
• [TypedMetadataDelegateImpl]
• [NullableMetadataDelegateImpl]
c) Storage Layer (Bottom):
• [Type-Specific Maps]
• Bytes Map
• Shorts Map
• Ints Map
• etc.
Important Elements
• Blue: Core interfaces
• Green: Implementation classes
• Yellow: Storage components
• Red: Exception handling (UnknownIdentifierException)
[Non-Null Values] → [Metadata]
[Null Values] → [NullableMetadata]
[Type Checking Layer]
↓
[Type-Specific Storage]
[Kotlin Property] ←→ [MetadataDelegate] ←→ [Storage]
Additional Notes
• Notes about multiplatform compatibility
• Relationship between typed and nullable access paths
Implementation Details
[Key (String)] → [Type Checker] → [Appropriate Storage Map]
Error Handling
A small section showing:
[Access Request] → [Type/Key Validation] → [UnknownIdentifierException]
Remember to include a note about the multiplatform nature of the project, indicating that this architecture works across JVM, JS, and Native platforms.