Craftsman is the workhorse behind the Wrapt framework and provides a suite of CLI commands for quickly scaffolding out new files and projects for your .NET Web APIs with simple CLI commands and configuration files.
For all the documentation on how to use Craftsman, visit wrapt.dev.
The last few releases have brought a ton of new features, but there are still several items I want to address before I slap the v1.0 sticker on things. I have some of the larger lifts below. Not everything here will be in the next release and this is certainly not an exhaustive list of everything, but I want to be open about what's on the horizon. 🌅
Have a request for something you don't see below? Join our discord and let's talk about it!
✅ Testing Optimizations
✅ Common Value Object Scaffolding
✅ Auth Server rewrite with Keycloak
🚧 Message Bus Enhancements
🚧 React Cleanup
🚧 React Permissions Integration
🚧 Json Schema for easier file scaffolding
✅ Updated CLI command structure
✅ OpenTelemetry & Jaeger Tracing
✅ Built in Domain Event support (with unit test scaffolding)
✅ Moved to Program.cs only format
✅ Added repository & unit of work abstractions for better testing and validation
✅ SmartEnum property scaffolding support
✅ Duende BFF scaffolding
✅ React scaffolding
✅ Dockerfile and Docker Compose scaffolding
✅ DDD promoted entities (private setters, factory methods, associated fakers)
✅ Huge permissions upgrade. Significantly simplified setup which resulted in a new library (HeimGuard) that can be used in any .NET project.
✅ New register:producer command
✅ Added soft delete capability
✅ Added Shared Kernel
✅ .NET 6 Scaffolding
✅ Docker utility updates for integration tests using Fluent Docker 🐳
✅ add:feature enhancement to add more than just ad-hoc features
✅ new:example command to generate example projects with associated templates
✅ Auth Server Scaffolding (In-Memory)
✅ Auditable entities
If Wrapt and Craftsman are saving you time and helping your projects, consider sponsoring me on Github to support ongoing Wrapt development and make it even better!
Time is of the essence. Before developing a Pull Request I recommend opening a new topic for discussion. I also haven't had enough PR interest to take the time and put together a contributing.md, but if you are interested, I will definitely put together a detailed writeup.
Sometimes Github notifications get lost in the shuffle. If you file an issue and don't hear from me in 24-48 hours feel free to ping me on twitter or Discord (pdevito3#4244). We also have own discord channel now for easy contact with me and larger community discussions!