Juhan Oskar Hennoste

I can reproduce similar times on my Windows 10 laptop with an HDD (~0.03 ms per query in-memory and ~170 ms per query writing to disk). For comparison, I wrote...

> Nuxt 3 has [extends](https://v3.nuxtjs.org/examples/advanced/config-extends/) to support this. [See extends status](https://github.com/nuxt/nuxt.js/issues/13367) > > There is an npm module for Nuxt 2, [nuxt-extend](https://github.com/nuxt-contrib/nuxt-extend) How exactly would extends solve this issue? Extends...

Maybe there already is an option for this, but it seems that currently the autocomplete only shows suggestions if you press tab. In most editors, the autocomplete starts showing suggestions...

Using `validate:"required"` has the problem that this makes the default value invalid, so something like `{"email": "", "password": ""}` would be considered invalid, which would be problematic if the default...

Now that ggez has new maintsiners, is there any update on when and how wasm support might happen?

This seems to be fixed in the latest version on GitHub master branch. Probably related to #98. Would be nice if the haxelib version was updated.

Is this issue resolved?

1.6.1 is now released. Is the issue resolved on that?

As an alternative, if adding a struct tag seems like too much of a break away from encoding/json, an alternative proposal would be to add a config option similar to...

Is there any hope of resolving this? When working with long-running code on windows this is extremely frustrating.