knallcharge

I'll check it out, if I find the time (or if APY doesn't come with an update for symfony 6).

not a typo, after the "fix" the code would not throw the ByteUnits\ParseException any more

Thanks for getting back. Can't change company policy, so also _Sigh_ for having to use Windows. I have setup a sample project here: https://github.com/Knallcharge/phpdox-test When building the project on Jenkins...

Same issue with symfony 4.4.8, PhpStorm 2020.1.1 Build #PS-201.7223.96, symfony Support plugin 0.20.195 Both use statements show the same behaviour, removing and re-adding does not help, invalidating cache does not...

Managed to get a workaround for this by adding a function for state_load_params: added this to buildDatatable() ``` $this->callbacks->setStateLoadParams( [ 'template' => 'datatable/_data_callback.js.twig', 'vars' => [ 'column' => $searchColumn, 'search'...

Looked further, because the factor 5 struck me and found something: I'm setting the pipeline in the AJAX options `('pipeline' => 5)`, removing this will resolve the issue (but of...

Method "Symfony\Component\Config\Definition\ConfigurationInterface::getConfigTreeBuilder()" might add "TreeBuilder" as a native return type declaration in the future. Do the same in implementation "Sg\DatatablesBundle\DependencyInjection\Configuration" now to avoid errors or add an explicit @return annotation...

Warning still shows in v1.3.0

I found a workaround, added this to the controller: `$this->events->set(['column_visibility' => ['template' => 'columnVisibilityEvent.js.twig', 'vars' => ['tableName' => $this->getName()]]]);` and added `columnVisibilityEvent.js.twig` like this: ``` function columnVisibilityEvent(e, settings, column, state)...

Thanks for pointing out, solved it with VirtualColumn already, was just wondering if it was me or actually an error :)