Sarkis
with this PR we may also need to update how clearSingle parses key from url
for the second one I don’t have any problems with the storage but it’s still useful to have control on the quantity of the keys per endpoint. Just an example,...
Hi, I'm sorry for the late reply, to much work. This project was developed as an quick solution to run UI to manage your graphQL entities, so it's mostly for...
thanks. Right now it's not possible, only if you will rewrite schema parser middlewhere to add Relay support. I don't use Relay, don't even have any projects that uses it...
@SharePointPro hey, sorry for the late response. I'm currently busy with another project. PR welcome, project has all test cases and everything to make it easier, otherwise I can't give...
Hi, just try: ```js const createType = require('mongoose-schema-to-graphql').default; ``` or ```js import createType from 'mongoose-schema-to-graphql'; ```
try new version from npm `2.7.1` it should be compatible with commonJS
Hi, sorry for late response. it is a good idea, right now you can use workaround for example: ```js createType({ name: 'User', description: 'an application user', class: 'GraphQLObjectType', schema: User,...
@HydraOrc hm, didn't thought about directly using API url, looks good, will try, thanks! But I think you need pipe `request.get` stream, instead of `r`, if you want to stream...
@andresmgot it also looks like when build is succeed and function deployment is started, kubless doesn't kill the job and job object just persist in k8s. And this is because...