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 have configured fill-request-fields-with-example="false", and this works for most of our properties. However, any that are type array still get the examples filled in. I noticed there was a similar fix already merged for the per-property x-fill-example setting, see #776; hopefully fixing this is as simple as adding the global check to the same place?
The text was updated successfully, but these errors were encountered:
Actually, this is a deeper problem. Looking at the code for that fix it is already trying to honor the global setting. And in fact, even when we set x-fill-example to "no" on a specific array property, it still gets filled in. So the fix does not work at all. Here is an example of such a property that is getting filled in inappropriately Rapidoc for our spec:
"areaOfInterestIds": {
"description": "The `id`s of the Areas of Interest to which notifications based on this template should be sent",
"example": [
"8145ebd1-7a8b-11ee-bc97-098b09a637c2"
],
"items": {
"format": "uuid",
"type": "string"
},
"type": "array",
"uniqueItems": true,
"x-fill-example": "no"
},
We have configured
fill-request-fields-with-example="false"
, and this works for most of our properties. However, any that are typearray
still get the examples filled in. I noticed there was a similar fix already merged for the per-propertyx-fill-example
setting, see #776; hopefully fixing this is as simple as adding the global check to the same place?The text was updated successfully, but these errors were encountered: