-
Notifications
You must be signed in to change notification settings - Fork 699
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with Constraint as (Query|Request)Param's requirements #726
Comments
@ClementGautier can you have a look? |
can you paste the exception? |
After some research, this don't seem to be related to FOSRestBundle because when i remove the Regex requirement, the issue is still here. I don't understand why because it worked before I update some vendors. I think the problem is more in the jms/serializer repos. Can you just confirm me that I'm using the feature the right way? |
This is definitely due to a bug in jms/serializer, not in this bundle because after removing the requirement, it still happen. Sorry for this is issue. |
ok .. |
An exception is thrown (when running phpunit) in JMS metadata when using new feature from #700.
Can someone confirm we can use this:
Edit: This is a strange bug, when I'm calling my api in the browser, it works, but when I'm unitesting it, an exception is thrown (coming from a PHP warning):
The text was updated successfully, but these errors were encountered: