compeller
compeller copied to clipboard
simonireilly
A strong typescript binding for your OpenAPI Schema that doesn't need generation and is not prescriptive in coding style
This PR introduces: ``` yarn compeller add createUser --path /v1/user --method post ``` A command for injection of a new path with an associated schema. The injection will ultimately lead...
closes: #25 We need to support common things like: - `GET /users/{id}`
Currently the type for ajv is inferred, from the type of the object. This object is inferred from the JSONSchema type. It looks as below: ```ts Ajv.compile(schema) ``` This double...
Currently, the typing in compeller has been growing from a _what can be made to work_ type specification but the actual typing needs to enforce the required format of the...
Compeller needs to support refs, because refs are used heavily in OpenAPI specifications which become very large. The specification itself will use refs to point at other declarations. ### MVP...
The path object of an OpenAPI specification is associated with the parameters declaration. Common use cases like `?limit=10&offset=0` should be supported. - [ ] feat: paths can be typed and...
Since we have a runtime write file, we need to improve that. Ideally we would have a default export from the compeller file (do we want that, I hate default...
Since we generate a location for schemas we should make it really easy for users to add schemas. ``` yarn compeller add-schema [name] ``` - The new schema should go...
Currently, the responder interface is passive and returns an `any` type. In order to allow a typed response, we should infer the type in the actual responder. This might be...
When need to allow for different request/response formats. In general, we could have two scenario's: - [ ] #34 - [x] #35 ## Adapters ### Option 1 We could configure...
Metadata
Owner
Metadata
A strong typescript binding for your OpenAPI Schema that doesn't need generation and is not prescriptive in coding style