Closed volga closed 1 year ago
Totals | |
---|---|
Change from base Build 4285805311: | 0.0% |
Covered Lines: | 1574 |
Relevant Lines: | 1574 |
Hi, @barbieri! Coverage action broke on this request and I opened a new request instead. I propose to close the current request and continue working in a new request. PR #227
@Volga thanks for your help, let me know if the argparse change makes sense (if you could use it, otherwise let me know how we could make it usable instead of just disabling the types).
Other than that, please squash both commits, since the first one is not relevant to be merged as is (it's being replaced by the second one).
@barbieri Great idea! I've committed it. I am closing the current request. Please review the code in PR #227.
We are testing Golang services that use the library https://github.com/99designs/gqlgen to generate the code. This library also uses a custom scalar Time type, but, unlike the sgqlc library, in it the Time type is a complete representation of the timestamp.
With the current changes, it is proposed to add the --disable-datetime-types argument to the client generation utility, which provides the ability to deactivate the use of custom datetimes types in the generated client.