Yes the json itself is not spreadable , i didn't really needed that feature so i left it that way , but well source is here feel free to make it spredable.
I think it should work , but the problem will be that you'll have to change the other node to have json input spreadable as well , add a binsyze for the query node otherwise there will be no way to know wich query go with wich json.
Actually an easier way will be to add all the json together with +(string spectral) node with the correct json formatting and query it as a single json , much more easy than dealing with binsyze stuff and at the end you got the same result.
The node for the list is also not spreadable , but could be without to much work , as well a binsyze output will be needed to identify the ouput data with the corresponding query.
Usually when i don't have time, i don't care about doing stuff i don't need , but i still share the result...
As alternative to that, fully spreadable:
((json-aselement,)) which parses JSON directly to XElement using the .NET builtin parser.
Of course, with XElement you still have the headache of caring about binsizes and stuff further down the expanding-lots-of-single-things-into-lots-of-spreaded-things road.
nice plugin, but wouldn't this make it "really" spreadable:
Yes the json itself is not spreadable , i didn't really needed that feature so i left it that way , but well source is here feel free to make it spredable.
yes, i think it's just that few lines above... if someone with json knowledge confirms that working, i can update the contrib.
though it's needed or not, i alwayys try™ to make new nodes asap*
I think it should work , but the problem will be that you'll have to change the other node to have json input spreadable as well , add a binsyze for the query node otherwise there will be no way to know wich query go with wich json.
Actually an easier way will be to add all the json together with +(string spectral) node with the correct json formatting and query it as a single json , much more easy than dealing with binsyze stuff and at the end you got the same result.
The node for the list is also not spreadable , but could be without to much work , as well a binsyze output will be needed to identify the ouput data with the corresponding query.
Usually when i don't have time, i don't care about doing stuff i don't need , but i still share the result...
As alternative to that, fully spreadable:
((json-aselement,)) which parses JSON directly to XElement using the .NET builtin parser.
Of course, with XElement you still have the headache of caring about binsizes and stuff further down the expanding-lots-of-single-things-into-lots-of-spreaded-things road.
sanch, hi
I used this plugin very usefully.
but, I have a trouble in parse of using JSON Array node.
{key1 :{key2:value2}, {key3:value3}, {key4:value4} }
this data could parse successfully.
but this data couldn't in case of just only json array except of key.{key2:value2}, {key3:value3}, {key4:value4}
maybe, I think JSON Array node always need path value.
I would like to filter bitcoin price from here
https://api.coinmarketcap.com/v1/ticker/?limit=10
but im not getting how to use this
@andresc4 see: https://discourse.vvvv.org/t/how-to-parse-json/16015