Cezar Neaga

is there also a way to configure it to reuse the fetcher and context? besides doing it manually?

our api is very big so it is split by domain into separate files. the baseUrl is the same for all, auth is the same for all. there isn't one...

but for our case a "merge .yaml files before use" would be better. because otherwise i'd need to merge the QueryOperation in the context

i get `Can't resolve $ref` errors from redocly 🤷🏻‍♂️

i cannot unfortunately. will try to investigate on my own why the merging fails. i think it may be that the refs are not namespaced properly and some conflicts appear....

> Probably related, I am getting the following dependency issue when running 'npm install' after a fresh download (degit). > > npm ERR! ERESOLVE unable to resolve dependency tree npm...

i am using pnpm.

@KyleAMathews could this PR work? would need this too! thanks!

you didn't miss it. if you did miss it, then so did i. how do you see this working?

Nik still keeps it running with new react versions. I have started a version 4 but progress is slow. We’re thinking of using Lerna, styled components, and some other goodies....