[
https://issues.apache.org/jira/browse/TIKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151374#comment-17151374
]
ASF GitHub Bot commented on TIKA-3082:
--------------------------------------
nddipiazza edited a comment on pull request #315:
URL: https://github.com/apache/tika/pull/315#issuecomment-653789371
@lewismc @tballison What do you think about swagger?
I want to take what Lewis did here and put the documentation within
swagger-annotations + swagger-jaxrs. This would remove the need for the openapi
yaml file and would instead put that documentation for the api inside the java
code within annotations. This would then make it so the
`${tikaServerEndpoint}/swagger.yaml` would produce the openapi yaml output and
will easier stay in sync with the api in the feature, while still getting the
benefit of the codegen / seamless import into postman / etc.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> OpenAPI for tika-server
> -----------------------
>
> Key: TIKA-3082
> URL: https://issues.apache.org/jira/browse/TIKA-3082
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Lewis John McGibbney
> Priority: Major
>
> On TIKA-2253, [~lewismc] asked:
> bq. I was planning on putting together an OpenAPI specification for Tika. Is
> anyone in favor of this?
> What do people think? How much will it change the current tika-server? What
> are the benefits?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
