Problems with Deno KV
This is just some code I made to test KV. However, it does seem to save anything.
2 Replies
I somewhat fixed it.
But is there a way of writing a schema or something for better code?
And how else can I improve the code?
Deno kv itself intends to provide a raw, low level interface, at least by now. More ergonomic APIs built on top of kv have been coming from userland. You can search for kv in #showcase. People have been creating ORMs, autoindexes, schemas and stuff
But IIRC, you can at least pass a type to
kv.get<T>