io.atomicbits.scraml.generator.codegen
The reason why we treat all actions of a resource together is that certain paths towards the actual action execution of the resource's actions may be overlapping when it concerns actions that have overlapping mandatory content-type and/or accept header paths.
The reason why we treat all actions of a resource together is that certain paths towards the actual action execution of the resource's actions may be overlapping when it concerns actions that have overlapping mandatory content-type and/or accept header paths. Although such situations may be rare, we want to support them well, so we pass all actions of a single resource together.
The resource whose actions are going to be processed (NOT recursively!)
A list of action function definitions or action paths that lead to the action function. Action paths will only be required if multiple contenttype and/or accept headers will lead to a different typed body and/or response (we don't support those yet, but we will do so in the future).
Created by peter on 23/08/15.