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
It'd be handy to have a fn that went the other way, so that you could take a string with vanilla GQL syntax and parse it back to clj/s/edn data. Could open up some nice opportunities for testing, too, since you could confirm that eg (v/data (v/graphql-query FOO)) would always be a no-op.
But purely a suggestion, and may be out of scope for what you want for venia.
The text was updated successfully, but these errors were encountered:
It'd be handy to have a fn that went the other way, so that you could take a string with vanilla GQL syntax and parse it back to clj/s/edn data. Could open up some nice opportunities for testing, too, since you could confirm that eg
(v/data (v/graphql-query FOO))
would always be a no-op.But purely a suggestion, and may be out of scope for what you want for venia.
The text was updated successfully, but these errors were encountered: