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
Would it be possible to expose the type of the polymorphic variant here instead of inlining it.
My use case is that I have a subscription and a query fetching the same things, and I don't want to store these things as a Js.t({. "feed": ...}) but instead extract the actual variant types and store those as a list in my app.
I first fetch the feed from the query, and then use subscriptions to update the feed by injecting new objects. Having a list of the above mentioned Js.t is way more awkward than just storing a list of the actual variant.
I'm okay with converting between the subscription and query types since they won't be the same thing. But not having to extract it first from a Js.t would help a lot.
The text was updated successfully, but these errors were encountered:
ylecornec
pushed a commit
to o1-labs/graphql_ppx
that referenced
this issue
Jun 3, 2022
* fix: drop env based configuration
* fix: drop env based configuration in favor of ppx-flags based
* Lean parse (mhallin#58)
* Simplify decoders
* Simplify
* make it even more efficient
* Add config option
* add feature flag
* make it work
* Make tests pass
* Test lean parse by default
* Remove Js.Dict.get runtime overhead
* remove comment
* fix enums
* remove comment
Co-authored-by: Jaap Frolich <jfrolich@gmail.com>
I have query which looks something like this
Which has the return type
Would it be possible to expose the type of the polymorphic variant here instead of inlining it.
My use case is that I have a subscription and a query fetching the same things, and I don't want to store these things as a
Js.t({. "feed": ...})
but instead extract the actual variant types and store those as a list in my app.I first fetch the feed from the query, and then use subscriptions to update the feed by injecting new objects. Having a list of the above mentioned Js.t is way more awkward than just storing a list of the actual variant.
I'm okay with converting between the subscription and query types since they won't be the same thing. But not having to extract it first from a Js.t would help a lot.
The text was updated successfully, but these errors were encountered: