Kai Schlamp

Since the latest release of `i18next-http-backend` (since 1.2.0) I also get the below Typescript error when setting the `loadPath` option and using `i18next-http-backend` and `i18next-fs-backend` in the same app. I...

Yes, I know. But unfortunately, Typescript doesn't seem to know, or better to say, mistakes types. ``` import i18n from "i18next" import Backend from "i18next-fs-backend" ... const createClient = ()...

Unfortunately, I have the same problem of missing namespace support. And as namespaces can be configured in so many ways (even when generating the i18next instance itself), I guess this...

Will this fix be merged for the next beta? When the query has non-optional parameters, you can't just do `invalidateQuery(getUsers, {})` but have to cast the empty object to `any`....

Yes, Prisma seed is a bit tricky to set up (especially with TS and modules), but I still would prefer the Prisma way. Maybe when creating a new Blitz app...

I guess the only way to support this feature is first to implement real distinct SQL queries (see #14765). Currently `distinct` [is done programmatically](https://www.prisma.io/docs/concepts/components/prisma-client/aggregation-grouping-summarizing#distinct-under-the-hood), which I guess is not an...

I also stumbled over this. For a custom language, I want autocompletion for variables that always begin with `$` (e.g. `$foo`). By default, neither filtering works with typing a `$`...

Same problem here also with a monorepo setup (using Gitpod, but shouldn't matter). I also get the error message "Test result not found.". Any workarounds yet?

I guess this depends on browser support of lookbehind which is not perfect https://caniuse.com/js-regexp-lookbehind

Some cookie support in hyperscript would be great as it is one of the only reasons why I sometimes use Alpine.js + js-cookie instead of HTMX + hyperscript.