Using gradle's builtin string replacement leads to complicated codegen because our generation requirements aren't quite that straight forward (see #74 for example). It may be worth considering moving to a proper templating engine such as pebble, hopefully one that doesn't add another dependency outside of something that could be downloaded from maven before the build script is evaluated.
Using gradle's builtin string replacement leads to complicated codegen because our generation requirements aren't quite that straight forward (see #74 for example). It may be worth considering moving to a proper templating engine such as pebble, hopefully one that doesn't add another dependency outside of something that could be downloaded from maven before the build script is evaluated.