What problem does it solve?
Designing Spiderly entities with correct attributes, relationships, and UI mappings ensures generated DTOs, validators, mappers, and admin UI align with business rules and developer workflows.
Core Features & Use Cases
- Enforces Spiderly conventions by requiring [SpiderlyEntity] on hand-written entities and guiding DTO generation and UI scaffolding.
- Documents base classes, including BusinessObject<T> and ReadonlyObject<T>, and explains how they influence IDs, timestamps, and CRUD scaffolding.
- Outlines property rules, explicit FK support, and relationship patterns (One-to-Many, Many-to-One, Simple/Multi Many-to-Many, and ordered one-to-many) with practical guidance for real-world models.
- Covers UI control auto-mapping and attribute-driven UI hints to ensure consistent admin forms and frontend bindings.
- Provides complete design guidance for configuring relationships (M2O, M2M, ordered O2M), file uploads, and UI control mapping across the codebase.
Quick Start
Provide a minimal hand-written entity class annotated with [SpiderlyEntity] including a navigation property, an explicit FK, and a basic CRUD-ready structure to demonstrate the standard design.