-
Notifications
You must be signed in to change notification settings - Fork 351
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
Configure RefResolver:$maxDepth? #181
Comments
Same issue here. Because of the commit #161 we started having issues. |
This is also required for our project. We either have to manually change the file after installation, or we'll need to fork the project. Would much rather just have a param we could set. |
@micahgodbolt why not submit a PR instead of working from a fork? If you are going to make a change that will help others, you should consider giving it back. |
@bighappyface oh I certainly would! I totally agree with contributing > complaining :) I was going to say that #184 already submitted one, but it seems you already closed that. I'll check with out PHP devs to see how they'd prefer to code that up. Do you have a preferred approach? |
I'll help with any PR that has support from the community. I don't think #184 accomplishes anything and closed it predicting that it would not pass community scrutiny. PRs are very welcome and the exclusive source of maintenance on this project. My only ask is that you submit changes with suitable tests and consider helping review other PRs in need of a review. |
RefResolver:$maxDepth = 42; |
Yes, you can do that. I guess my point was that I felt kind of dirty overriding a global static property, that is used by all instances of RefResolver. |
I kept getting
The maximum stack depth has been exceeded
errors, and I couldn't figure out what was going on. Finally, I found a public staticRefResolver$maxDepth
resolver property. I tried setting it to 20 (default was 7), and the schema validated fine.I feel a little funny overriding a public static property on a test utility. What would you think about making this a configurable property on the
RefResolver
instance?The text was updated successfully, but these errors were encountered: