Thanks for pointing this our and glad to see you're actively working with IRIS. As Vic has pointed out although the ObjectScript VSCode extension has been announced, we haven't yet released our first release 1.0. See the https://community.intersystems.com/post/intersystems-joins-open-source-objectscript-vs-code-effort message from @Raj Singh .
In fact, the BPL editor (IDE) is only available in Studio and the Management Portal. We'll fix this. Although you certainly can use the existing extension, it is not an InterSystems offering. We are in the process of revising recommendations to use Atelier. Once the VSCode extension is released we will have documentation for it.
For now, if you're working with productions, I'd recommend using InterSystems Studio or the Management Portal. Atelier can also be used but doesn't have any advantage over Studio.
Thanks for finding this. We'll fix it. We have two sets of Python doc: the automatically generated reference (from source code comments) https://docs.intersystems.com/irislatest/csp/docbook/Python-Native/irisnative.iris.html#irisnative.iris , which you were using and the User's Guide and Reference https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=BPYNAT_refapi#BPYNAT_refapi_iris_get-client-version , which has the correct information.
Obviously we generated the reference with an earlier version of the software and didn't update it after the change. We will fix that.
I would recommend using the User's Guide and Reference https://docs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=BPYNAT rather than the automatically generated one.
If you find any problems in the User's Guide and Reference, you can click on the Help us improve this page tab on the right and we'll fix it. We haven't yet added it to the automatically-generated reference. You can also send us a comment at email@example.com.
The WRC is InterSystems Worldwide Resource Center, our support group. No need to contact them over this, but they are a great resource for many issues.
Thanks for the comment. Is this description clearer?
The recommended way to create a REST service is to create an OpenAPI 2.0 (also called Swagger) description for the REST service and use that to generate the REST service classes. If you are implementing a REST service defined by a third party, they may provide this OpenAPI 2.0 description. See the OpenAPI 2.0 Specification for details about the format of an OpenAPI 2.0 description. The following topics describe how to use the /api/mgmnt service to do this.
In the first step, generate the REST service classes, as follows:
Thanks again and feel free to use the "Help us improve this page" link on any of our documentation pages to send us a comment.
Log in or create a new account to continue