Reda
Reda
Did you manage to find a solution to this problem ?
Wow that's a big difference... For reference: http://cosmicrealms.com/blog/2014/08/29/benchmark-of-node-dot-js-json-validation-modules-part-3/
+1 though not part of JSON, this would be useful for example to enforce "javascript interfaces", or to document these.
> Same issue here... signature seems to be incorrect for some reason. Using `Walletlink` with `ethers.js` web3 provider... > > I see that in repo are already more opened issues...
I don't remember exactly but i:t has to do with this https://github.com/ethers-io/ethers.js/blob/d3b7130ed6ec50b192eb7f33905eaa327d65eee2/packages/providers/src.ts/web3-provider.ts#L35
For reference. https://github.com/loomnetwork/loom-js/issues/278
Which network is it? Ext-dev or plasma?
Sometimes it is not feasible to do yet another query to get options, you'd want to include available actions in the entity: ``` { _links: { self: { href: "https://blog/posts/example-1" ...
What if the available methods are variable, for example POST would be available for an open discussion (imagine this is the type of resource) but not for a closed one....
@mikekelly I see what you mean. Conveying these rules in the state of the resource or making it explicit tends to be more of an developer (consumer) experience (DX, gush...