Closed SergioCasCeb closed 10 months ago
Name | Link |
---|---|
Latest commit | 073b8d5b9c8d33b89fe8838e8f14538f354a85a8 |
Latest deploy log | https://app.netlify.com/sites/thingweb-playground/deploys/65328ba2ab105d0008ee1414 |
Deploy Preview | https://deploy-preview-514--thingweb-playground.netlify.app/ |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Implemented minor fixes with the new close tab prompt, so that if a user opens an example while the close prompt is open, it will close the prompt.
Momentarily removed the "Save as" button until HTTPS is implemented for Playground
What is your opinion @danielpeintner about that? Will node-wot reject an unknown protocol in the future or will it try best effort?
I guess it would be wrong to reject unknown protocols. The current node-wot code does not make any assumption. Hence I agree with your statement "we should accept unknown protocols"
. Hence I agree with your statement "we should accept unknown protocols"
But shouldn't we at least give a warning? It feels a bit wrong to be confident about something that doesn't "exist"
But shouldn't we at least give a warning? It feels a bit wrong to be confident about something that doesn't "exist"
I don't feel strongly about it and a warning might be okay. On the other hand, do we warn people in the TD spec about protocols we don't know yet?
On the other hand, do we warn people in the TD spec about protocols we don't know yet?
There are plans to add protocol validation and this will indeed be a question. So far "htv:methodName":"GETTER"
is accepted
@danielpeintner what do you think now? It is only a gray text on the right hand side
@danielpeintner what do you think now? It is only a gray text on the right hand side
Fine by me
Added a similar error handling and message just like the ones utilized for OpenAPI and AsyncAPI.