-
## Describe the Bug
When using global `path-parameters` in the `api.yml` file, the Fern OpenAPI Generator does not respect these global parameters. As a result, the generated OpenAPI specification …
-
### Is your feature request related to a problem? Please describe.
The [OpenAPI spec](https://spec.openapis.org/oas/v3.1.0#style-examples) allows you to define parameters that can be rendered as `c…
-
Code
```ts
const projects_list_default_limit = 10;
const projects_list_max_limit = 100;
export const listProjectSchema = z.object({
limit: z.coerce
.number()
.min(1)
.max(project…
-
Root cause I believe is: https://github.com/python-attrs/cattrs/issues/321
Repro:
```python
import json
from uapi.openapi import SchemaBuilder, IntegerSchema
from uapi.attrschema import build…
-
It was suprising to find out that I can't create a collection from an existing, deployed OpenAPI spec.
How it could/should work:
- I can "create a collection from existing OpenAPI spec" by pasting…
-
Hi there,
is there a way to generate two different versions of the OpenAPI specification and distinguish between internal and external routes? Our idea is that we want only specific routes to be in…
-
Thank you for providing this example. I believe the template doesn't apply here.
Everything works as described however when trying to access the OpenAPI definition through /docs, I'm getting the fo…
pietz updated
2 months ago
-
Hello, is it possible to specify `servers` in the generated `swagger.json` in any way, besides manually editing it?
I am using an external configuation file `openapi-configuration.yaml` together wi…
-
```yml
openapi: 3.0.2
servers:
- url: /api
info:
title: Demo
version: 0.0.1
paths:
/demo:
get:
responses:
200:
$ref: "#/components/responses/DemoB…
-
Now that ?model is gone and we treat it like all other inlinable sub-objects, `?inline=*` will inline/show all inlinable entities (model, groups, resources, resource docs, meta). However, "model" is d…