Karam
Karam
Ok, I'll take a look and see what I can do...
Are we getting one step closer to single table design in amplify? Writing resolvers in JavaScript might make this transition easier.
@danrivett did any downstream issues come up from your monkey patch?
If this is an easy fix maybe i'll try my luck with a PR
@tywalch is there something else required?
Thanks @tywalch. I was looking for a typecheck command to run. I've since found test:types. I will try to find some time to dig in deeper. This is an intense...
My very easy and very unsophisticated workaround is to create multiple fields for each env with hard-coded values.
We're starting to feel the issue of not having local mocking that supports all the features we're using in amplify. When we onboard new developers they make frequent changes (especially...
How about `amplify mock`creates a copy of the schema and comments out the `@searchable` directives for me? That way I don't accidentally drop it in production when i yolo push...
Another solution we're considering is removing `@searchable` from our schema and getting by with `@key`s. We don't think our users will notice since search is limited to a few fields.