Raathi Kugarajan

@gregveres the optional chaining change is released as a part of https://github.com/Raathigesh/majestic/releases/tag/v1.7.0 @pdashford If you could provide a sample repo, that would be really helpful to investigate.

Curious to know the use case behind using over an `https` connection?

Feel free to reopen if this is a blocker but closing this for now.

Majestic is meant to be used locally in the same way as a local dev server so I'm trying to understand the benefits of having a secure connection.

@justusbluemer I'm glad that you find the tool useful. Are you open to contributing the change?

@NickBolles I'm not against it but didn't get the time or motivation to work on it yet. Reopening the issue. Feel free to send a PR if you are interested.

@pavelzubov Thanks for looking into it. Yes, the[ https options ](https://github.com/prisma-labs/graphql-yoga/blob/master/src/types.ts#L84)can be provided through the start method of the server. The doc also mentions a bit more about https option...

@pavelzubov The URL to connect to the server is in https://github.com/Raathigesh/majestic/blob/master/ui/apollo-client.ts. Is changing those URLs to `wss` be enough? If so, we could introduce a command-line argument which when provided...

So that means we have to provide the cert and key to the `graphql-yoga` server. We can accept the paths to the cert and the key as command-line arguments and...

@pavelzubov That looks good to me. Let's do that 👍