Announcement

**Isomorphic** · 24 Nov 2025, 07:01

Thanks for the error report. We have now fixed this; the fix will be in all builds from 13.0 onwards, as of tomorrow, November 25th.

**claudiobosticco** · 2025-12-23T16:04:01

SmartClient Version: v13.1p_2025-12-23/AllModules Development Only (built 2025-12-23)

Hi, I see that the issue is fixed - thank you very much (but https://www-demos.smartclient.com/sm...s/openapi.html still returns a blank page).

I also noticed that, with a pair of operationBindings like the following:

Code:

<operationBindings>
     <operationBinding operationType="fetch" description="foo"/>
     <operationBinding operationType="fetch" operationId="bar"/>
</operationBindings>

both of them appear in the documented POST API calls, plus a third one:

.../RESTDataSource/myDs/fetch/(unnamed default operation)

Additionally, I see the calls for the SimplifiedREST protocol listed after those for the AdvancedREST protocol. Is it possible to disable the SimplifiedREST ones?

Finally, I don’t see the description for the fetch operation reflected in the SimplifiedREST call.

**Isomorphic** · 2025-12-24T00:47:58

www-demos is actually meant for private demos, although for some reason, people keep linking it...

It seems likely you want these docs:

https://smartclient.com/smartclient-...openapiSupport

Let us know if that wasn't the thing you wanted.

We'll get rid of the "foo" / "bar" stuff which was clearly debug code that leaked.

As far as wanting to disable the SimplifiedREST version, can we ask, why would you care about that? Are you trying to ensure that anyone calling your APIs has a certain level of sophistication? Or perhaps it's a DDOS defence thing?

**claudiobosticco** · 2025-12-24T08:53:23

Originally posted by Isomorphic View Post

www-demos is actually meant for private demos, although for some reason, people keep linking it...

It seems likely you want these docs:

https://smartclient.com/smartclient-...openapiSupport

Let us know if that wasn't the thing you wanted.

Thanks for the heads up - I’ve updated my bookmark accordingly.
However, the following link, which is mentioned at the bottom of the OpenAPI documentation, still returns a blank page:
https://smartclient.com/smartclient-...s/openapi.html

Originally posted by Isomorphic View Post

We'll get rid of the "foo" / "bar" stuff which was clearly debug code that leaked.

As far as wanting to disable the SimplifiedREST version, can we ask, why would you care about that? Are you trying to ensure that anyone calling your APIs has a certain level of sophistication? Or perhaps it's a DDOS defence thing?

Regarding the SimplifiedREST APIs: yes, my thinking was that in some scenarios I might want to require callers to use only the AdvancedREST protocol.

I’m also not sure I explained the other issue clearly. With a test case like the one from my first post - which previously triggered the error:

Code:

<operationBindings>
     <operationBinding operationType="fetch" description="foo"/>
     <operationBinding operationType="fetch" operationId="bar"/>
</operationBindings>

I now see the two expected calls correctly documented, plus a third one with “(unnamed default operation)” appended to the URL:

[cut]/RESTDataSource/myDs/fetch/(unnamed default operation)

Additionally, I don’t see the "foo" description (which I added to the default fetch operation) reflected in the SimplifiedREST section of the generated documentation.

Announcement

OpenAPI support error

Comment

Comment

Comment

Comment