2015-09-10, 19:24
Where should problems be reported when finding a problem in compliance when using a plugin and the json transport?
For instance using the SoundCloud plugin the Player.OnPlay notification packet does not comply with the documented spec.
Specifically params>data>item>artist is returned as an array:
{
"jsonrpc": "2.0",
"method": "Player.OnPlay",
"params": {
"data": {
"item": {
"artist": [
"Guardian Politics Weekly"
],
"title": "US presidential candidates and Northern Ireland ??? Politics Weekly podcast",
"track": 1,
"type": "song"
},
"player": {
"playerid": 0,
"speed": 1
}
},
"sender": "xbmc"
}
}
But the api specifies a string for type song:
"artist": {
"default": "",
"type": "string"
},
I can understand if the app is supplying bad data (ie multiple artists), but it is the responsibility of the engine to not to participate populating with incompatible data.
Normally data validation belongs on the front end but Kodi has to expect anything and everything from open plugins
For instance using the SoundCloud plugin the Player.OnPlay notification packet does not comply with the documented spec.
Specifically params>data>item>artist is returned as an array:
{
"jsonrpc": "2.0",
"method": "Player.OnPlay",
"params": {
"data": {
"item": {
"artist": [
"Guardian Politics Weekly"
],
"title": "US presidential candidates and Northern Ireland ??? Politics Weekly podcast",
"track": 1,
"type": "song"
},
"player": {
"playerid": 0,
"speed": 1
}
},
"sender": "xbmc"
}
}
But the api specifies a string for type song:
"artist": {
"default": "",
"type": "string"
},
I can understand if the app is supplying bad data (ie multiple artists), but it is the responsibility of the engine to not to participate populating with incompatible data.
Normally data validation belongs on the front end but Kodi has to expect anything and everything from open plugins