Artur Czemiel

https://zeus.graphqleditor.com/page/graphql/variables.html

take a look here. Maybe it is not perfect solution, but we will improve it soon

Wait Ill try to improve the plug-in system so produce lib script can take them into consideration

Of course we should do that. I have already implemented this kind of validation in new version of graphql-editor. Can you contribute copy it to zeus?

Wait for 5.0. 5.0 main goal is to make everything easier for contributors. Now code generation is a mess , in 5.0 zeus will be developable by every mid/senior dev.

I can add some zeus config in the future. Exporting enums is considered bad practice, const enums are much lighter but get hidden during transpilation

A lot of people asked for const enums before instead of enums

ok I'll try and test that with different projects and if it won't cause problems I will change it

Good idea we can work on it in 5.0!

of course. I am in the process of rewriting zeus a little bit to support new `graphql-js-tree` library, so it may be a little bit delayed, but definitely worth adding!