Kiryl Mialeshka

Put the draft implementation https://github.com/tailcallhq/tailcall/pull/807 that currently implements only `@protected` directive for fields and types. For jwt currently use mocks inside the code. For possible options for `@auth` directive I'm...

For now I'm thinking to implement next structure of the schema directive: ```graphql schema @auth(JWT: { jwks: { file: "jwks.json" } }) { query: Query } ``` this is to...

Same issue for me, would be great If issue was fixed by changing default rendering or at least allow to change settings for rendering

I think the docs about the `recursive` option is misleading as example works exactly opposite to docs. Settings `recursive: false` will put folders in archive as is

I'm working on pr that will provide access as I've suggested in the description

Do we really need to capture the output separately? Consider this: - instead of calling some function from the lib we can start the binary programmatically and capture it's output....

> > ``` > > * instead of calling some function from the lib we can start the binary programmatically and capture it's output. > > ``` > > but...

> > I believe it'd better represent end user experience and we will test the actual output instead of testing that some data has been written somewhere that won't mean...

I'm working by myself on the comments I provided in a separate branch, please ignore them

The issue is related to https://github.com/swc-project/swc-node/issues/700 In previous major version @swc-node/[email protected] mocks are working right I'm expecting that https://github.com/swc-project/swc-node/pull/714 will fix the problem