Closed ninjaniels closed 9 months ago
You seem to be correct - we'll check
Dear @ninjaniels ,
Please check out our latest release v1.461, we made a modification to the OpenAPI parser that should fix this.
Kind regards,
Thanks! It's working now. This is a great feature and will save us a lot of time
Describe the bug We have just implemented ALOps OpenAPI, a great feature in ALOps for auto-generating the Open API Specification file to all our API endpoints. However the URI for bound actions on API pages is incorrect. The URI is missing /Microsoft.NAV..
Perhaps this is outside your control if all of the magic happens through other services back-end, but it's make it or break it for us if we can use this feature or not.
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior The URI to a bound action should be///companies()/()/Microsoft.NAV., but the generated URI is ()/ .
Screenshots Output from ALOps OpenAPI generated documentation
Correct URI from manually maintained documentation