In the Swagger UI, the model/model schema are documented in the Parameters section. When I import the same documentation into the Azure API Management portal, parameters with .NET data types are documented but the complex object/model/model schema in the request body loses its documentation.
I saw an update for Model Schema support Azure API Management adds support for Swagger model schemas.
But it did not work when I tried it in the API Portal.
Do anyone know how to import the Model Schema Documentation into the Azure API Management Portal?
Is this update available in New Portal only? And if so when will API management be available in New Portal?
Note: I am using Swagger 2.0 documentation from Swashbuckle in Visual Studio 2013.
Model schemas are imported if they are in the Swagger file. If that's not the case your saw, can you please send your Swagger file to apimgmt at microsoft dotcom so that we can take a look at the file.
I was able to repro this issue and have fixed it. Hopefully, I will be able to get the fix in the next release.
Related
I am having troubles with updating my OData Client.
I would refer to How to call bound functions / actions inside Java client using SAP Cloud SDK? where people from SAP helped me alot, thanks!
Issue is, I wanted to update dependency to last version of SAP Cloud SDK because of new functionality that supports bounded functions and actions.
Back then (4 months ago), I had written myself documentation how to generate and use OData Java client properly, using SAP Cloud SDK. Quite a number of people was succesful back then with installing.
Now, 4 months later, I cannot generate properly client. I have installed lombok and also set it as reference in Eclipse and am using latest Eclipse (2021-06).
I will put screenshots of my errors. It says like my properties are not generated properly and that 1 method is missing - getOdataType().
These problems just started to occur last 2 weeks or so.
Thank you in advance!
I am lost in dependencies and tools:
I previously use the following tool to generate code for my swagger webservices.
swagger-codegen-cli
https://mvnrepository.com/artifact/io.swagger.codegen.v3/swagger-codegen-cli/3.0.13
https://github.com/swagger-api/swagger-codegen
Then I noticed the following tool, and thought this was a successor:
openapi tools generator
https://github.com/OpenAPITools/openapi-generator
https://openapi-generator.tech/docs/installation.html
But the code that is generated uses different annotations and seems older.
Could somebody tell me, are these 2 tools related to eachother and which one is the more recent version?
From the OpenAPI Generator FAQs
What is the difference between Swagger Codegen and OpenAPI Generator?
Swagger Codegen is driven by SmartBear while OpenAPI Generator is
driven by the community. More than 40 top contributors and template
creators of Swagger Codegen have joined OpenAPI Generator as the
founding team members. For more details, see the Fork Q&A.
Swagger is a trademark owned by SmartBear and the use of the term
"Swagger" in this project is for demo (reference) purposes only.
One way to compare open-source projects is using https://openhub.net.
e.g. OpenAPI Generator vs Swagger Codegen.
From the activity and community graphs, openapi-generator seems to be a lot more active.
Its seems that openapi is in a messy state currently. I'm also confused on which generator to use... And I want to write a custom generator.
GRPC is in a much better state. Every generator is a plugin and the core is well maintained, are the community is not forking.
Update:
Our company has agreed to keep using OpenAPI. We're now using the new OpenSource variant of OpenAPI: openapi-generator.tech/
We've extended the python generators to tweak the generated code.
We're also using client generators in TypeScript and considering Kotlin and Swift for our mobile apps.
In the end it works well. If you're not ready to go binary with GRPC, OpenAPI is a nice alternative. It does requires a bit more, my experience with GRPC is that its a no-brains solution. "It Just Works".
But your miles may vary.
I am searching for a solution to build and publish the AWS Lex bot via .NET SDK or via any other API.
Any help will be appreciated.
I just recently developed a working Amazon Lex Chatbot using .NET SDK and one of the tools that helped a lot was the GitHub Repo that AWS maintains for C#. Do note that they use .NET core and not .NET framework.
Alternatively, if you want to use the REST API (which is what I did), you can go to the .NET documentation guide that Amazon also maintains. These REST API can be accessed via the Nuget package that you can get inside Visual Studio itself.
It is so confusing, can someone help me demystify?
Does MuleSoft support OpenAPI 3.x.x specification as of today? Also what is this RAML 1.0 specification? Do we really care about RAML specs when dealing with MuleSoft?
The OpenAPI Specification (OAS), originally known as the Swagger Specification, is a specification for machine-readable interface files for describing, producing, consuming, and visualizing RESTful web services.
RAML, API Blueprint are same kind of IDL for REST API.
MuleSoft have a product called Anypoint Platform API designer that can help design only RAML API specifications, so it does NOT support OAS 3.0.0.
However, the product support the OAS 2.0. You can import an OAS ZIP or JSON file from your file system or from a URL. The importation converts the OAS to RAML. Basically, it is OAS to RAML converter.
The OAS 3.x support has been released in MuleSoft in API Designer, Anypoint Exchange, and Anypoint API Community Manager since June 26, 2020.
You still can not use OAS 3.x in the implementation and manually have to convert it to RAML or OAS 2.0. But API consumers can still discover, learn, and consume the APIs seamlessly, regardless of the specification language.
More in this link. https://docs.mulesoft.com/release-notes/platform/oas3
Here you go. there is a latest release on OAS3.1.0 support in mule4.
Anypoint studio, designer, exchange supports new features such as callbacks and links.
If you want to migrate mule3 to mule4 use mule migration assistant.
https://docs.mulesoft.com/release-notes/platform/oas3
Please have a look at it.
I am looking to create an application that allows a user to update Microsoft Team Foundation Server work items when performing certain things in the app.
Has anyone done anything similar themselves and if so what is the best way to make the updates to the TFS work items from within the app?
There is a Java API which is linked below:
http://www.microsoft.com/en-us/download/details.aspx?id=22616
Other than that a few google searches resulted in the following discoveries:
http://msdn.microsoft.com/en-us/library/bb130146.aspx
The link below tells you how you can create new work items via a URL:
http://msdn.microsoft.com/en-us/library/bb822136%28v=VS.90%29.aspx
** As per jessehouwing's comment below *
This only works on 2008 and 2010 I suspect. There migth be a similar Url for 2012 and 2013, but the whole WebAccess feature was rebuilt using ASP.NET MVC instead of WebForms, so the wi.aspx no longer exists. I'm not aware of an alternative.
Visual Studio Online an Team Foundation Server 2013 are gaining more and more json based REST Api's and have recently been upgraded to support OAuth for authentication. Some of these API's are still in preview, but they're a great resource for a mobile platform client.
For older versions of Team Foundation Server and the On-premise version you can either install the OData service, or build a custom webservice that employs the TFS Client Object Model internally to create the work items.
Should you want to build your webservice on top of a non-microsoft-platform, then you can employ the Java SDK for Team Foundation Server. This will allow you to communicate directly to TFS from a Linux or Mac server.
TFS 2013.4 will be able to show more pages in full screen mode without any chrome around it.