George Lemon
George Lemon
The best use case scenario is when working with APIs. I want to use `jsony` to serialize/deserialize objects in requests & responses. For example ```nim type Product = object id,...
```nim import std/json, pkg/jsony type Thing = object name*: string interval*: int AnotherThing = object name*: string interval*: int proc newHook(x: var Thing) = if x.interval == 0: x.interval =...
This is great! I'm curious about numbers, any benchmarks?
Well, yes, the main idea around `@import` is to be able to expose functions from the host language into Tim templates. This is going to be the expected behavior when...
Currently, exposing a function is possible by doing this ```nim import pkg/tim # initialize tim engine var timEngine* = newTim("templates", "storage", currentSourcePath()) # initialize the local module # note that...
This is sexy! I love it
I'm not familiar with Windows system. You can make a PR if you want
First, generate your package using `nimble init` as binary app. In `mypackage.nimble` add `requires "kapsis#head"` A working example should be: ```nim import pkg/kapsis import pkg/kapsis/cli proc oneCommand*(v: Values) = displayInfo("Hello")...
`checksums` package is outdated. Get the latest version
Not easy in the `main` branch. The `rewrite` branch will have a better way to handle this. For example, `type` function https://github.com/openpeeps/tim/blob/f4ce4752b658de720537fa3fface46061e909410/src/tim/engine/stdlib/libsystem.nim#L118-L130