Guilhem Niot

Thanks for this initiative but I'm not sure that's a bad thing to have several packages doing project management. For example [`recent-projects`](https://github.com/EXSyst/recent-projects) discover new projects only when you open them...

Hi, I encounter the same issue, did you by any chance found a workaround since then? I was thinking about adding a small random variation to the locations but that's...

Ok actually I was able to mitigate the issue by setting `maxZoom` to 15: ```js import React from 'react'; import { Marker } from 'react-native-maps'; import MapView from 'react-native-map-clustering'; const...

:+1: What about: ``` yml dunglas_action: must_be_public: - Symfony\Component\Security\Core\Authorization\Voter\VoterInterface ``` and make all the others private (or maybe also add an option for that)? IMO every service should be able...

@dunglas that's indeed already possible but it complexify the installation of the bundle. Including it here would also permit to follow the core autowiring behavior (private by default).

Note that prototypes will be included in sf 3.3 and you'll be able to do what you want: ```yml # app/config/services.yml services: AppBundle\: resource: ../../src/AppBundle/MyAwesomeService autowire: true AppBundle\: resource: ../../src/AppBundle/MyAwesomeService/{Query}

Since the controller is public, it should rather be deprecated first.

@d-tylczynski-foodpanda I released a new version of https://github.com/FriendsOfSymfony/oauth2-php but it doesn't solve this issue as pointed by @Spomky

I just tagged oauth2-php 1.2.3, these constants have been deprecated in it, does it fix your issue ?

@tomasjav could you submit a PR doing the change please? :)