Chris Drackett
Chris Drackett
as a way to possibly avoid some circular import issues I wonder if it would be valuable to put all the generated code into a single file.
based on https://github.com/mobxjs/mst-gql/issues/270 the following is what we currently do if a query/mutation has variables but they all happen to be optional: ``` variables: { label?: string, message?: string }...
We recently removed the mobx open collective links from this project as contributions to that pool don't actually affect this project. That being said, I'm curious if it is worth...
examples 1 and 5 are currently broken due to the changes in https://github.com/mobxjs/mst-gql/pull/265. This has to do with how the above changes interact with `relativeDependencies`. I decided to keep the...
right now we only expect a single ID field. However, in the case a user has more than one ID field on an object mst-gql will not know which one...
with these here its possible to get circular import issues. Maybe we should throw these in there own file. /cc @special-character
this came up in #225. At the moment we don't compress our bundle. There might also be other low hanging fruit we're missing around our build process so this issue...
for example `RootStore` in `reactUtils` and potentially enums in `RootStore.base`