Benoît Geeraerts

@DonCallisto this actually happens on forwarded routes. Fabien Potencier actually explained [here](https://github.com/symfony/symfony/issues/854#issuecomment-1123531) that _route should not be used because it is only for debugging purpose.

In a similar issue, I did resolve it using the RequestStack instead: ``` /** @var Symfony\Component\HttpFoundation\RequestStack $requestStack -- can be DI'ed */ $gridManager->createGrid() ->setSource($source) ->setRouteUrl($requestStack->getMasterRequest()->getPathInfo()); ```

The command I launch : ``` ../vendor/bin/mageconfigsync --env=preview ../config/config.yaml ``` config.yaml ``` 'magento_ee-1.14.1.0': default: &magento_ee_stock #some values reduced because they don't matter prod: default: &prod_default

@punkstar Follow up information, if I blank any field on Magento config, it sets it to null. So maybe a fix could be ``` if ($value === '') { $affected_rows...

I can confirm the above statement. Mage_Core_Model_Resource_Db_Abstract::save is calling _prepareDataForSave Mage_Core_Model_Resource_Db_Abstract:: _prepareDataForSave is calling _prepareDataForTable Mage_Core_Model_Resource_Abstract::_prepareDataForTable is calling prepareColumnValue on write adapter Varien_Db_Adapter_Pdo_Mysql::prepareColumnValue states ``` switch ($column['DATA_TYPE']) { // cases...

Here is the JMESPath equivalent: ``` [?event_type=='click'].{status: attributes.send_status, type: attributes.activity_type} ``` And if you want a single object, like `jq` is giving you: ``` [?event_type=='click'].{status: attributes.send_status, type: attributes.activity_type} | [0]...

@sivel Thanks for the feedback, it makes all the sense. I was also wondering since I saw that @bcoca intentionally reworded the documentation from tuple to list. I'll update accordingly.

And now I am wondering if we should align this line for the list matter too : https://github.com/ansible/ansible-documentation/blob/6f1cf471c8f44970b6b5cb285d3a2a352a0f726e/docs/docsite/rst/playbook_guide/playbooks_filters.rst#L2016 I.e. from ``` # with path == 'nginx.conf' the return would be...

The behaviour I would expect when doing a ```merge(`{"a": 1}`, null)``` would be to get `{"a": 1}` as a result, as `null`, is a valid JSON object. Or at least...

Thanks Stéphane, this was duly noted, I pinned the version I am using at a really specific version, because I red the linked page already. I am still a recent...