Damien
Damien
This shouldn't be in the API reference! https://jkcfg.github.io/reference/std/latest/modules/std_param.html#param https://github.com/jkcfg/jk/blob/db0ce0c/std/param.ts#L81
It'd be nice to start working towards integrating some common toolchain-things in `jk` itself. This is taking the nice properties of the go toolchain which integrates linting, formatting, testing, ......
It'd be nice to start working towards integrating some common toolchain-things in `jk` itself. This is taking the nice properties of the go toolchain which integrates linting, formatting, testing, ......
At the moment we have to explicitly tell `merge` the rules to merge two objects. For instance: ```js const pod = { spec: { containers: [{ name: 'my-app', image: 'busybox',...
We probably want to solve #128 before looking at what the typescript version would look like.
This is the first important use case we are targeting, we should make it easy for people to go from 0 to a working k8s example, removing hurdles on the...
We've been careful crafting the importing code to not important beyond the script directory. There are some cases where the user wants to specify additional import directories though: if the...
It'd be nice to have `examples/README.md` as a table of content for our examples to users can quickly search for what they'd like to do. To enforce that, we could...
It'd be nice to be able to copy resources easily. For instance, when generating npm modules in [module-template](https://github.com/jkcfg/module-template) I copy the LICENSE file.
It'd be nice to move away from the complexity of having `npm` and `package{,-lock}.json`. ```js import { api } from "https://github.com/jkcfg/[email protected]/api"; ``` - unpkg offers npm modules over http: https://unpkg.com/...