Patrick McElhaney

@kaikun213 thanks for the feedback! > Just stumbled upon this library, amazing exactly what I searched for! Great job, it was really easy to get it up and running with...

1.0 was released a couple of months ago! 🚀 Closing this issue.

Maybe there can be a grace period with backwards compatibility. If a `paths` directory is detected, Counterfact will continue to use the old structure but print a warning with migration...

Could write a migration script. I just don't want to inflict unexpected changes on people. After 1.0 I'm going to start promoting. I'd rather get this sort of thing out...

How would we specify multiple APIs? I'm thinking something like an OpenAPI-collection.yaml file that has a list of references to OpenAPI files and (optionally) the paths to which they map....

I'd rather do a config file in order to keep the CLI arguments from getting too verbose. If there's no standard we'll invent one.

Okay, you've convinced me not to do a config file. Instead we'll support @dethell's original suggestion as well as @jivewise's wildcard suggestion. ```sh npx counterfact ./api/open-api-1.json ./api/open-api-2.json my-second-schema.yml ./api npx...

> > Adding a way to specify file wildcards would be really nice, something like `npx counterfact ./api/*.yaml ./api -g` > > It's true you can just run it multiple...

Looking at this again. ``` Usage: counterfact [options] [openapi.yaml] [destination] ``` Without changing the CLI we can only put one file in the `[openapi.yaml]` slot. I can think of three...

Yeah I think it could be either a Base64 encoded string or a Blob or a stream.