Inconsistent accessibility of ValidationBehavior and BaseBehavior<TView> classes. #844
Closed
MaximG1234
started this conversation in
New Feature Discussions
Replies: 1 comment
-
Closed as per the Community Stand-up discussion here: https://youtu.be/N9wMcBP4jtg?t=2889 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently
ValidationBehavior
andBaseBehavior<TView>
is declared as a public class which implies to me that it is 'encouraged' to use this as a starting point for your own Behaviours. Yet a number of key methods are defined asinternal
specifically:I wanted to create a
ConditionalMultiValidationBehavior
based on the MultiValidationBehavior where I would leverage attached properties to create AND OR conditions for a generic collection of behaviors but because the above methods are internal I am stuck.IMHO either these entire classes should be marked as internal (which they obviously shouldnt) or all the underlying methods should be accessible. From an extremely cursory review I cannot see a strong reason why these methods have been marked as internal anyways.
Beta Was this translation helpful? Give feedback.
All reactions