Bob van de Vijver

Results 97 comments of Bob van de Vijver

That is indeed true, the existing implementation is a rate limiter based on the amount of messages on the transport and blocks the complete worker.

This is not caused by this bundle, but it is required by one of your other dependencies. You can run `composer why sensio/framework-extra-bundle` to see where it comes from.

It looks like this actually also causes the reported finding to be incorrect, as that seems to compare the full item including the full path.

@MrLexisDev I believe this is fixed with https://github.com/FriendsOfSymfony/FOSJsRoutingBundle/pull/462

@TysonAndre I just hit the need for this one, consider the following code snippets: ```php /** @extends ServiceEntityRepository */ class LocationRepository extends ServiceEntityRepository { /** @use FindByInstituteTrait */ use FindByInstituteTrait;...

@ntaylor-86 If you are open to switch to another package based on this one (features and methods are not fully compatible), maybe you can add this there as well? See...

@thenewwazoo I believe this is caused due to the OccupancySensorRouter implementation (I am working on the Homey integration, and am using your implementation from time to time to know what...

The change made in #803 was actually BC breaking in my case: the bundle started using a different object constructor by default, breaking my implementation.

In my scenario I'm using `json-merger` which uses `jsonpath`, so I do not think I'm able to be explicit here. The line that is throwing the error is https://github.com/dchester/jsonpath/blob/master/lib/grammar.js#L102. ```...