You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 12, 2021. It is now read-only.
The only part Wox actually got right is the method key.
jsonrpc: While I can see why this can be omitted, I don't think it's a bad idea to be explicit about what protocol is being used when communicating with other plugins/processes, specially for future backward compatibility.
params: The specs and Woxs doc both mention the params key for the parameters, but for some reason the actual payload use parameters instead.
id: All requests that expects a response (ie the query function) should include an ID, which should also be sent back in the response along with the result. This is currently omitted.
The specs also mention an error key in our response, but as far as I can tell that data is also being ignored.
The text was updated successfully, but these errors were encountered:
In the docs it's said that Wox use the JSON-RPC Spec to communicate with its plugins, however, it doesnt seem to actually follow the specification.
A valid request to a plugin, according to the spec, looks like this
This is the payload our plugins currently get from Wox
The only part Wox actually got right is the
method
key.jsonrpc
: While I can see why this can be omitted, I don't think it's a bad idea to be explicit about what protocol is being used when communicating with other plugins/processes, specially for future backward compatibility.params
: The specs and Woxs doc both mention theparams
key for the parameters, but for some reason the actual payload useparameters
instead.id
: All requests that expects a response (ie thequery
function) should include an ID, which should also be sent back in the response along with the result. This is currently omitted.The specs also mention an
error
key in our response, but as far as I can tell that data is also being ignored.The text was updated successfully, but these errors were encountered: