[asterisk-bugs] [JIRA] (ASTERISK-24300) API docs don't conform to stated Swagger version

Matthias Urlichs (JIRA) noreply at issues.asterisk.org
Sat Jan 13 07:37:40 CST 2018


    [ https://issues.asterisk.org/jira/browse/ASTERISK-24300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241520#comment-241520 ] 

Matthias Urlichs commented on ASTERISK-24300:
---------------------------------------------

OK, this bug is >three years old, swagger has been renamed to OpenAPI, is now at version 3, and the problem still hasn't been solved.

IMHO Asterisk 16 should use an uptodate version of -Swagger-OpenAPI. Benefits include a reasonably-specified protocol (Swagger 1.1 is not) and the fact that there is a verifying async Python3 client library for OpenAI 3.0, while nobody in their right mind spends any time on implementing asyncio support for what exists for 1.1.

Thoughts?

> API docs don't conform to stated Swagger version
> ------------------------------------------------
>
>                 Key: ASTERISK-24300
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24300
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Documentation
>    Affects Versions: SVN, 12.5.1, 13.0.0-beta1
>            Reporter: Bradley Watkins
>
> For at least events.json, the stated Swagger version (in that case 1.2) is not what's actually in use.  It appears, based on some historical asterisk-dev mailing list posts, that an in-progress version of 1.2 was used.  However, now that 1.2 has been finalized I think it's important to update the models and code generation tools to that spec.
> As it stands, any tools built to work with the 1.2 standard will not function correctly against Asterisk's api docs.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list