Project Maintenance and Proposed Improvements

[pwelter34]

Hi everyone,

I’d like to open a discussion about the current state of this project. Chris kindly granted me some permissions to help maintain it, and while I’m eager to contribute, I’ve found it challenging due to the project's current condition.

The project is significantly behind in addressing issues, reviewing pull requests, and managing technical debt. I’m motivated to improve things, but I’m also conflicted about how best to proceed. Here are a few observations and concerns:

• Technical Debt: The codebase is outdated, with older frameworks and package versions.
• Performance Bottlenecks: Mapping FieldIdentifier to validation paths is slow, especially with large object models.
• Unclear Code: Some components, like IntersectingCompositeValidatorSelector, are difficult to understand and may need reevaluation.
• Assembly Scanning: I believe this approach is problematic and should be removed. Validators should be registered via dependency injection to keep concerns separated.
• Breaking Changes: I’m considering several significant changes that would modernize the project, but I’m unsure how well these would be received. Core functionality would remain intact.

I’ve also considered starting a new library from scratch. However, this package is widely used, and I want to do what’s best for the community. We don’t need yet another Blazor FluentValidator library if we can improve this one.

Here are some proposed changes (in no particular order):

• Rewrite Validation Mapping: Improve performance and reliability by redesigning how FieldIdentifier maps to FluentValidator paths, with comprehensive test coverage.
• Remove Assembly Scanning: Validators will be explicitly set or resolved from DI based on the EditContext model.
• Rework Validation Result Surfacing: This may introduce breaking changes for consumers who manually retrieve validation errors.
• Modernize the Codebase: Update to leverage the latest framework features and tooling.
• Integrate .NET 10 Validation Abstractions: Align with upcoming platform improvements for better long-term support.

My goal is to either clean up this project or have a new library ready by the time .NET 10 is released. I’d love to hear your thoughts, concerns, or suggestions.

Thanks,
Paul

[pwelter34]

Unfortunately, I’m no longer able to maintain this project. The NuGet key has expired, and I don’t have a way to renew it. Rather than trying to patch things up, I’ve decided to channel my efforts into a complete rewrite.

Introducing Blazilla — a fresh take on FluentValidation for Blazor. This new project was built from the ground up to address many of the lingering issues in the original implementation. If you're looking for a modern, actively maintained solution, I encourage you to check it out.

🔗 GitHub – Blazilla

Thanks for your support!
~ Paul