Skip to content

Conversation

@Tihomirov-Vasiliy
Copy link

@Tihomirov-Vasiliy Tihomirov-Vasiliy commented Dec 24, 2023

resolve #31

&& !type.IsEnum && !type.IsValueType
&& !type.IsPrimitive
&& type != typeof(string)
&& !type.GetInterfaces().Contains(typeof(IEnumerable));

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess that should be considered as breaking change. If someone is right now using e.g. List as Body parameter, after this change validation will stop working for this parameter.

Copy link
Author

@Tihomirov-Vasiliy Tihomirov-Vasiliy Jan 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes you're right. You can use any collection properties with custom type and add FluentValidation's validators for them, thank you for mention it in your issue
I relaxed checking by deleting the IEnumerable check

@mvdgun
Copy link
Member

mvdgun commented Jan 15, 2025

Closing this one, will revisit the whole topic of supported types when designing v2. Thank you for your contributions @Tihomirov-Vasiliy!

@mvdgun mvdgun closed this Jan 15, 2025
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.

Simplifying TypeExtensions.cs IsCustomType method

3 participants