Lars Marius Garshol

This might work: ``` [for (.) { "EmpID": .peci_Worker_Summary.peci_Employee_ID, "ChangeEvent": .peci_Effective_Change.peci_Derived_Event_Code, "PayRateType": .peci_Effective_Change.peci_Position.peci_Pay_Rate_Type } ] ```

I'm tempted to add this to the experimental module so we can get some experience with it in practice before nailing the exact behaviour. I'll see if I can get...

This is an interesting point. I've been thinking about this issue quite a lot ever since I started the project. For my own uses I've decided having these IO dependencies...

At the moment the only way to do it is to plug in a custom Java function. Can you elaborate on what you need? Does have to be specifically UUIDs?

I see. I guess there are three options. 1. Write a function to randomly generate an ID that's long enough to *probably* be unique. ``` def range(n) if ($n <...

I'm not familiar with that component, so I don't really know. Why would you want to pass the functions as a query parameter, though? Can't you always pass the same...

If you want to define the function in JSLT you can just do that inline. ``` def plusone(x) $x + 1 plusone(2) ``` I was thinking about JSLT functions defined...

You're right. This was sloppy of us. We definitely need error handling here. The pattern we've used elsewhere is to have a second fallback parameter that gets returned if the...

Yes, I think this looks entirely reasonable. I need to review the details in how the gradle files were split, but the rest looks very nice. Regarding how to package...

@alexanderkjeldaas Are you still working on this?