Serguei Okladnikov

Migration to 9.0.0 to use generators is blocked due to [graphql-compose-mongoose#275](https://github.com/graphql-compose/graphql-compose-mongoose/issues/275) discussion - there is no possibility or documentation about how to apply middleware.

@nodkz, Is actually the problem related to add/etc resolver methods? The problem is in api mismatch between modules. The module [graphql-composer](/graphql-compose/graphql-compose) declares resolver function params as object: ```js async ({source,...

@nodkz, thanks, I tried to create a test case that demonstrate a problem and I get some more info which allow us to be one step closer to source of...

Some more external ways. Special additional method with different name for `addResolver`, for example `addStandartResolver` or `addResolverClassic`. Another way is wrapper function that slightly resembles cpp casting, to cast resolver...

Yes, it's not easy. It's good that you found a workaround. In order to fix it is necessary the same configuration to reproduce. It is best to take one of...

Solved in #481

Installing before publishing is a little tricky due to lerna. It may be solved by adding to `package.json` something like this: ```json "dependencies": { "micro": "file:./micro/packages/micro/micro-v10.0.1.tgz" }, "scripts": { "preinstall":...

Just to clarify. What exactly is meant by generated dataProvider? The introspection queries returns the data. The existing dataProvider forms internal data structures based on this data. And then it...

I would like to notice may be obvious that: * building the dataset should allow users to use it without involving special webpack configuration etc., so that users can use...

Looks good. You would have done a pr right away, we would have seen that the tests pass.