Vignesh Venkatasubramanian Vaidyanathan
Vignesh Venkatasubramanian Vaidyanathan
Not sure where to inquire for this: HttpConfig for https client seems to ignore allowSelfSigned: ```javascript const { HttpsClientFactory } = require("@node-wot/binding-http"); const servient = new Servient(); servient.addClientFactory(new HttpsClientFactory({ allowSelfSigned...
Yes sure. Personally I would say that if there is more than one form of subprotocol possible with the same http method and URL, then subprotocol field can be made...
I changed my mind. I think its fine if you just add a warning.
Hi, I have following use case: 1) nullable properties of fixed type - For example, I have the following property definition ```json "state": { "title": "state", "description": "current state machine...
That would make sense why it does not validate correctly. However what if I want `null` instead of `"null"` The NullSchema is written as follows in TD: > "Metadata describing...
Also serializing None to "null" instead of null does not make sense.
a plain null also raises an issue: ```json "state": { "title": "state", "description": "current state machine state if state machine present", "const": false, "readOnly": true, "writeOnly": false, "oneOf": [ {...
Hi, any update on this?
I re-read the issue. I think I get it now, the absence of output schema for actions indicate no return value from the server. The absence of input schema can...
Ah okay!! then this issue can be closed because there is inherent meaning in not having a schema as well.