I set kimai up by following the documentation (development install), and kimai (in dev environment) is working fine.

Then I cloned this repo into var/plugins. When I run bin/console kimai:bundle:demo:install, I get following error:

❯ bin/console kimai:bundle:demo:install

Starting installation of plugin: DemoBundle ...
===============================================

                                                                                                                        
 [ERROR] Failed to install database for bundle DemoBundle. Migrations configuration key "name" does not exist.

Commenting out the line just moves the error to "table_name" does not exist

I have created a copy of an already existing PDF template and saved it unter var/export/myexport.pdf.twig. I modified it to my needs and this worked pretty well.

Now I want to add custom rounding to the duration field where some math is implied. Since I was not able to achieve this just with twig filters, I would like to add an extra field like duration_rounded and do the calculation of this value in PHP.

What would be the best / update safe way to implement this?
Is it possible to register to a hook or extend the controller?

Fresh installation: when calling up the plug-in page, the error appears:
An exception has been thrown during the rendering of a template ("Warning: Array to string conversion").

The solution was:
Line 171 in var/plugins/DemoBundle/Resources/views/index.html.twig

{{ value }}
replace with
{{ value is iterable ? value|join(', ') : value }}

Hi Kevin
Thanks for this extensive hero demo of a plugin.
I was able to achieve some things with it, and learn how to survive better, in general...
Still, Symfony is a long way to go.

I'm now trying to re-implement my old Indesign XML Exporter from V1.

But at this stage I think I need to ask directly, since I seem to hit a solid wall, and from the past hours of trial'n'error it seems wise:

I extended the plugin with an exporter, that I think will serve as a minimum to get Indesign XML out in the end. However I also tried the "Invoice" route, since it allows userland'ish restrictions.

• Is it true that all of the up-to-now implemented ways to do Invoice are (forced) template based?
• Is it true that everything based on RendererInterface does require a template?
• Is final class ServiceInvoice the place where templates-are-mandatory is hardcoded? Or where would be the place to build a hook on?

I'm not sure if there is a benefit in a template for this kind of playout, but maybe I'm wrong.

Best wishes
Manu