[jira] [Assigned] (OFBIZ-12344) Additional findings and possible enhancements

["Michael Brohl (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OFBIZ-12344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Brohl reassigned OFBIZ-12344:
-------------------------------------

    Assignee: Lukas Finster  (was: Michael Brohl)

> Additional findings and possible enhancements
> ---------------------------------------------
>
>                 Key: OFBIZ-12344
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-12344
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: rest-api
>    Affects Versions: Trunk, Upcoming Branch
>            Reporter: Michael Brohl
>            Assignee: Lukas Finster
>            Priority: Minor
>
> This is a Jira to collect findings, discussion points and enhancements.
> It's primarily a convenience issue to make it easy to put together thoughts and ideas without having to create Jira issues immediately. Once a point gets more shape, a Jira is created for it.
>  
> Points:
>  * the ids for the API blocks in the Swagger UI are not taking the verbs into account which leads to same ids for different blocks with the same service name
>  
> Solved 
>  * it seems that only the first GET API is displayed in the Swagger UI
>  * the Swagger UI does not display GET resources with path parameters and subressources like
> {code:java}
> /parties/{id}/permissions{code}
>  * reason for it seems to be that openapi.json does not contain the path while application.wadl has it
>            -> the service parameters must match a path parameter else it will not be displayed, which is correct
>  * the generated openapi.json shows errors in [https://editor.swagger.io/]
>  ** "Header parameters named "Authorization" are ignored. Use the `securitySchemes` and `security` sections instead to define authorization."
> I guess the openapi generation must be changed, investigating...
>  ** "Structural error at paths./....parameters.0 should have either a `schema` or `content` property"
> the generated parameters from the service definition do not have a schema entry generated
>  ** the same applies to the WWW-Authenticate header in the responses
>  * it also shows warnings
>  ** "Header parameters named "Accept" are ignored. The values for the "Accept" header are defined by `responses.<code>.content.<media-type>`."
>           -> see OFBIZ-12426



--
This message was sent by Atlassian Jira
(v8.20.10#820010)