Niels Keurentjes

It should be noted that support for advanced environment variables was [added in Symfony 3.4](https://symfony.com/blog/new-in-symfony-3-4-advanced-environment-variables) and currently this bundle still supports 2.x.

> We would like to also be able to mark an entire API as deprecated. Repeating some internal discussion: Came here to upvote this point. The scenario is all too...

For the underlying discussion: especially when using deployments in for example Kubernetes you should not rely on command parametrization. [Config should be in the environment](https://12factor.net/config).

I very much support the proposed changes, as I have also faced the surprise of default recipes including the Stimulus boilerplate that I had to strip and delete right away....

I actually started a new project quite recently and am in a position to switch to RC. Will do so happily. Must say I'm surprised there's still no really good...

Upgrading was a breeze, upgrade guide works fine, barely had to change any code except for the changed exceptions. Application is working as before (syncing AD users, groups and their...

Same for photos btw (just trying): ``` Error thrown while running command "graph:azure:sync -svv". Message: "'GET' request to https://graph.microsoft.com/v1.0/users/{id}/photo/$value returned 404 {"error":{"code":"ImageNotFound","message":"Exception of type 'Microsoft.Fast.Profile.Core.Exception.ImageNotFoundException' was thrown." ``` Catching the...

There is no viable PR available and we are not actively developing this feature or planning to.

In general we ourselves now mainly using Vue for fully clientside tables :) The issue more or less got caught up by technology.

I don't understand the issue like this, seems like this is in how you use Mongo, not our bundle.