Kirill Agalakov
Kirill Agalakov
- to be more aligned with `fp-ts`
I suggest adding some kind of rule to allow extending external configurations like [it's done in eslint](http://eslint.org/docs/user-guide/configuring#extending-configuration-files). I have different project configurations in external npm package (linters, code inspections, webpack...
OpenAPI 3.0: - Requests: - [ ] single file uploads - [ ] upload as part of a multipart request - [ ] file array in a multipart request -...
Add: - resolver - parser - typescript-language serializer (no need for css since css-custom-properties can be inlined in `body :root` /cc @sutarmin
- we should support flexible server path configuration: - https://swagger.io/docs/specification/api-host-and-base-path/ - https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#server-object-example - https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#server-variable-object
```yaml components: schemas: echo: description: echo type: string messages: echo: payload: $ref: '#/components/schemas/echo' ``` This piece will result in ```typescript import { echo, echoIO } from '../../components/schemas/echo'; export type echo...
```yaml parameters: - name: times in: query schema: $ref: './shared.yaml#/components/times' ``` Current implementation assumes that there will be a separate run of generation for referenced entities in foreign spec. However...
As the codebase grows, new languages and specs are added, to better control tests and builds we need to turn the project to monorepo and split the code into several...
https://github.com/sketch-hq/sketch-file-format/blob/master/schema/layers/page.schema.yaml
Current implementation ties inner schema structure (paths, definitions, components etc.) to output directories so that we cannot use different names and directory structure. We should split schema and fs cursors:...