You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
that is because process substitution in bash (at least) does not provide facility to customize file extension:
➜ echo<(yarn schema.graphql)
/dev/fd/63
this is useful when the schema is generated via another command. allowing to explicitly specify schema extension would allow to bypass creating temporary files which is currently required to make it work.
is this something which might be accepted to the project? if so I can try taking a stab at this but first wanted some feedback if this is something which might be considered
The text was updated successfully, but these errors were encountered:
currently graphdoc does not have an option to specify schema extension/type as cli flag:
as such as makes some shell workflows impossible which involve process substitution:
➜ yarn graphdoc --schema <(yarn schema.graphql) --output docs ✗ Unexpected schema extension name:
that is because process substitution in bash (at least) does not provide facility to customize file extension:
this is useful when the schema is generated via another command. allowing to explicitly specify schema extension would allow to bypass creating temporary files which is currently required to make it work.
is this something which might be accepted to the project? if so I can try taking a stab at this but first wanted some feedback if this is something which might be considered
The text was updated successfully, but these errors were encountered: