Vignesh Venkatasubramanian Vaidyanathan comments

Results 7 comments of


                                            Vignesh Venkatasubramanian Vaidyanathan

Unusual behavior when configuring HTTPS from config file

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...

events without subprotocol might be causing unexpected behaviour

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...

events without subprotocol might be causing unexpected behaviour

I changed my mind. I think its fine if you just add a warning.

InteractionOutput - no schema/schema.type and the expectations of the value() function

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...

InteractionOutput - no schema/schema.type and the expectations of the value() function

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...

InteractionOutput - no schema/schema.type and the expectations of the value() function

Also serializing None to "null" instead of null does not make sense.

InteractionOutput - no schema/schema.type and the expectations of the value() function

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": [ {...