Example Scenarios:
1. User has a inline constraint like 'min(0'. Following is the current error message. Include the information about the controller and action for easy diagnosis.
_The inline constraint resolver of type 'DefaultInlineConstraintResolver' was unable to resolve the following inline constraint: ' min(0'_
2. User defines a constraint like: {id: min(0)}
Here there is a blank space between characters ':' and 'm'. This is probably because user might want to make it clear.
_The inline constraint resolver of type 'DefaultInlineConstraintResolver' was unable to resolve the following inline constraint: ' min(0)'._
Also consider error scenarios when user defines invalid routes on RoutePrefixes too.
Comments: I believe the current behavior is the expected behavior. Users get an appropriate error message when their inline constraint is not recognized.
1. User has a inline constraint like 'min(0'. Following is the current error message. Include the information about the controller and action for easy diagnosis.
_The inline constraint resolver of type 'DefaultInlineConstraintResolver' was unable to resolve the following inline constraint: ' min(0'_
2. User defines a constraint like: {id: min(0)}
Here there is a blank space between characters ':' and 'm'. This is probably because user might want to make it clear.
_The inline constraint resolver of type 'DefaultInlineConstraintResolver' was unable to resolve the following inline constraint: ' min(0)'._
Also consider error scenarios when user defines invalid routes on RoutePrefixes too.
Comments: I believe the current behavior is the expected behavior. Users get an appropriate error message when their inline constraint is not recognized.