You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using a list as example, which is a valid JSON. But the documentation doesn't show that example.
To reproduce
Steps to reproduce the behavior:
Generate an openapi spec with the following item (I believe the fact that it's a list is the issue. Other fields work well.
"street_address_alias": {
"items": {
"type": "string"
},
"type": "array",
"description": "Other known street addresses for the property. When searching for a property\nby address, these aliases will also be matched.",
"example": [
"123 Main St",
"125, Main Street"
]
},
Generate the doc
The example holds the key's name instead of the example.
Expected behavior
I'd expect to see ["123 Main St", "125, Main Street"] in place of street_address_alias in there.
Screenshots
On the left, the description was pulled. But on the right, the example wasn't.
Version
Fern Version: 0.18.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
We are using a list as example, which is a valid JSON. But the documentation doesn't show that example.
To reproduce
Steps to reproduce the behavior:
Expected behavior
I'd expect to see
["123 Main St", "125, Main Street"]
in place ofstreet_address_alias
in there.Screenshots
On the left, the description was pulled. But on the right, the example wasn't.
Version
Fern Version: 0.18.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: