-
-
Notifications
You must be signed in to change notification settings - Fork 848
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
NelmioApiDoc parser location #156
Comments
I also wondered this a while ago, and there is only something which could be problematic, I think: This means the DunglasApiBundle should have a dependency on |
@ogizanagi yes it's exactly why I've opened the PR on NelmioApiDoc initially. On another hand, I've no problem having NelmioApiDoc in the |
Then we have our answer 😄 How would you proceed if some features targeting the nelmio api doc behavior requires some configuration ? |
I feel like the fact Nelmio related stuff is located in another bundle is quite a big issue, especially until the api bundle has its first stable release (For instance, the I think the nelmio related stuff should move back into the bundle. It could be required in |
Fixed by #410 |
Hello, I have a simple question: why put the Nelmio documentation extractors in the NelmioApiDocBundle ? I don't think that the DunglasApiBundle specific PR have a place in the source code of the Nelmio project, what do you think of it ?
For example, I want to create this PR : nelmio/NelmioApiDocBundle@master...mRoca:feature/dunglas-avoid-infinite-recursion , and I would like to add some tests to prevent infinite recursion with circular entities relations with the same serializer groups. As this items are DunglasApiBundle specific, add them in the NelmioApiDocBundle doesn't seem normal.
Other example with this potential PR (wip) : nelmio/NelmioApiDocBundle@master...mRoca:feature/dunglas-add-max-depth . In order to add a default MAX_DEPTH option in the Nelmio doc, I would like to add a config option, or something like it.
The text was updated successfully, but these errors were encountered: