Closed jricher closed 1 year ago
Name | Link |
---|---|
Latest commit | df76190b1dc3f6abf2c12b63290299770bca8bdc |
Latest deploy log | https://app.netlify.com/sites/gnap-core-protocol-editors-draft/deploys/634971ee06439e0008556b0e |
Deploy Preview | https://deploy-preview-453--gnap-core-protocol-editors-draft.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 settings.
Makes sense, it's aligned with the behaviour of the rest of the doc
This reformats the object-type key proofs to be defined in terms of types, in parallel with interaction start methods. Now instead of default field values, you can have either an object with parameters or a string with strictly specified behavior. This should be less susceptible to confusion than the previous definition which allowed partial objects and implied a large set of possible combinations that the receiver would have to deal with.