Naming Conventions Checklist

Version: 2.0
Scope: Namespaces, type prefixes, and naming conventions.

See Class Hierarchy and Naming & Build for details.

• [ ] Unit names follow WvdS.<Category>.<Component>.pas
• [ ] Mirrors Microsoft .NET structure with WvdS. prefix
• [ ] Example: WvdS.Web.Mvc.Controller, WvdS.Web.Http

• [ ] Abstract base uses TWvdSCustom prefix
• [ ] Public base uses TWvdSBase prefix
• [ ] Concrete classes use TWvdS prefix
• [ ] Pattern: TWvdSCustomXxx → TWvdSBaseXxx → TUserXxx

• [ ] Classes: TWvdS* (e.g., TWvdSRouter)
• [ ] Interfaces: IWvdS* (e.g., IWvdSActionResult)
• [ ] Exceptions: EWvdS* (e.g., EWvdSRoutingException)
• [ ] Interfaces have GUID for DI container

• [ ] Namespace mirrors MS pattern with WvdS. prefix
• [ ] Classes use language-appropriate WvdS prefix (TWvdS, WvdS)
• [ ] FFI functions use wvds_ prefix (Rust)
• [ ] COM/ActiveX uses WvdS.<Component> pattern
• [ ] Descriptive names (no single letters except loops)
• [ ] No abbreviations unless well-known (e.g., URL, HTTP)

Version: 2.0 (Split)
Author: Wolfgang van der Stille

Back to Code Checklists | Review Checklists