miragejs-open-api
miragejs-open-api copied to clipboard
asantos00
Generate miragejs code based on an OpenAPI Specification
Bumps [handlebars](https://github.com/wycats/handlebars.js) from 4.5.3 to 4.7.7. Changelog Sourced from handlebars's changelog. v4.7.7 - February 15th, 2021 fix weird error in integration tests - eb860c0 fix: check prototype property access in...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [y18n](https://github.com/yargs/y18n) from 4.0.0 to 4.0.1. Changelog Sourced from y18n's changelog. Change Log All notable changes to this project will be documented in this file. See standard-version for commit guidelines....
Bumps [yargs-parser](https://github.com/yargs/yargs-parser) from 13.1.1 to 13.1.2. Changelog Sourced from yargs-parser's changelog. 15.0.0 (2019-10-07) Features rework collect-unknown-options into unknown-options-as-args, providing more comprehensive functionality (ef771ca) BREAKING CHANGES rework collect-unknown-options into unknown-options-as-args, providing...
Based on openAPI entities, generate mirage models: - Use models on handlers instead of hardcoded JSON
Note: This is not a plausible solution, it is just something that works with open api v2, we gotta abstract this somehow
Objective: - We can import this file and use it without touching it
Generate the following configuration: ``` const server = new Server({ baseUrl: 'https://api-url.com/blablabla/api', namespace: '/v1' }); // uses namespace v1 server.get('cenas', () => {}) server.namespace = '/v2'; // uses namespace v2...
Currently, the package only supports OpenAPI v3, would be cool to abstract this away so we can support both (branch incoming with it "barely" working for v2)
- Build a CLI command that enables to specify options like: - openApiUrl (local or remote) - outputPath - Docs