Sacha Greif
Sacha Greif
This would also make it easier to get rid of `resolveAs`, which while very handy introduces an extra concept that wouldn't be needed if there was an easier way to...
See https://github.com/VulcanJS/Vulcan/tree/apiSchema
This also means moving `relation` out of `resolveAs`, which probably makes sense anyway.
Here's a diagram: 
An added benefit is that API schemas only need to be defined on the server, which lightens the client bundle a tiny bit. Also a common problem with these fields...
 We could even have a separate database schema to mirror the API schema and hold fields that exist in the database but *not* in the API, since those...
Blog post WIP: https://medium.com/@sachagreif/vulcan-1-16-apischema-dbschema-7a85655dca26
Should this be on the context though? That feels weird since the context is not specific to a mutation or a permission check. I'd probably pass a fourth `options` argument...
Yeah… maybe another advantage with Redis is that you don't risk to overload your main server's memory? I could see that happening if your cache is not well-configured and just...
As pointed out by @doronrk there are two areas where TypeScript could help: 1. Add types to Vulcan core code 2. Add more validation to Vulcan app code By 2....