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
With current implementation, in case where there is request body for the API, the generated spec always presents that the request body is optional (which is not marked with required).
It seems that there is no way to mark required for RequestFieldsSnippet, such as optional() or required() method. Instead, we might leverage attributes, Map<String, Object> to indicate that the requestBody is required.
Is this reasonable?
The text was updated successfully, but these errors were encountered:
With current implementation, in case where there is request body for the API, the generated spec always presents that the request body is optional (which is not marked with required).
AS-IS
TO-BE (if the request body is required)
It seems that there is no way to mark required for
RequestFieldsSnippet
, such as optional() or required() method. Instead, we might leverage attributes, Map<String, Object> to indicate that the requestBody is required.Is this reasonable?
The text was updated successfully, but these errors were encountered: