Matt Beiswenger

I also found out that class-based validators are not working when using a nested changeset structure, for example ``` const validations = { person: { firstName: validatePresence(true) lastName: new CustomValidator()...

Also if it's currently not possible to inject a service into a class-based validator, should we at least remove `@service ajax` from the example in the README?

Also I have verified that the cache is changing for the query and the computed property is not changing.

@josemarluedke Thanks for the response. After doing some digging through other repos that use this library, I stumbled upon [ember-caluma](https://github.com/projectcaluma/ember-caluma) which uses [similar patterns](https://github.com/projectcaluma/ember-caluma/blob/56dd6d1dfeb2385e405466021d654ba994a0e657/addon/components/cfb-form-list.js) with ember-concurrency. Still not convinced that...

@MichalLytek Do you need to have an existing field in your prisma schema for `@FieldResolver` to work? For my use case, I'm hiding a `clientSecret` field in the schema but...

I also have a use case for this, trying to use [additional parameters in the Okta API](https://developer.okta.com/docs/reference/api/oidc/#request-parameters)

Sorry, I should have been more specific. I'm using Python 3.7.0 which has sqlite3 version 2.6.0 as a Python package. But, the sqlite version on my computer is 3.24.0.

Yep, it's version 3.24.0. I did try upgrade to 3.28.0 but was still getting the same error.

@craigfay Our team switched to postgres in local development to match our server configuration. This was able to fix the issue. Sorry, but I never found a way to resolve...