Skip to content

Conversation

@alexx-grand
Copy link

There is a need to remove FluentValidation on ComponentBase disposed

There is a need to remove FluentValidation on ComponentBase disposed
@alexx-grand
Copy link
Author

Fix for #155 #93

@teneko
Copy link

teneko commented Jun 29, 2025

This solution has several issues:

  1. It introduces a potential hidden breaking change if EditContext ever implements IEquatable or overrides GetHashCode.
  2. It shifts state management to a static context, breaking the logical binding to a single FluentValidationValidator instance.
  3. If two separate FluentValidationValidator components are used with the same EditContext, event unregistration is handled in a first-in-first-out manner rather than by identity, which can lead to incorrect behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants