You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a pathfilter to remove paths, the calls to removeAnnotation are slow.
On my code, it takes around 0.3s for each call to it. I think that I have 333 endpoints
it is "traverseAnnotations" which is slow, not the detaching, as if I comment it, it still take the same time
$this->traverseAnnotations($root, function ($item) use ($remove) {
if ($iteminstanceof \SplObjectStorage) {
foreach ($removeas$annotation) {
//$item->detach($annotation);
}
}
});
I don't know if it can be optimised.
Generating a swagger takes 45s with a filter that remove almost all endpoints, while without filter it takes 8 seconds
edit: on my code, i can remove all code after $callable($root) on traverseAnnotations, because the filtered path is directly written. I'm not sure if it's necessary to parse all properties to know the path ?
The text was updated successfully, but these errors were encountered:
Well, the tests still pass without recursion. However, removal of unused components might be affected without. Perhaps we can make the recursive part optional...
When using a pathfilter to remove paths, the calls to removeAnnotation are slow.
On my code, it takes around 0.3s for each call to it. I think that I have 333 endpoints
it is "traverseAnnotations" which is slow, not the detaching, as if I comment it, it still take the same time
I don't know if it can be optimised.
Generating a swagger takes 45s with a filter that remove almost all endpoints, while without filter it takes 8 seconds
edit: on my code, i can remove all code after
$callable($root)
ontraverseAnnotations
, because the filtered path is directly written. I'm not sure if it's necessary to parse all properties to know the path ?The text was updated successfully, but these errors were encountered: