Closed lawrencegripper closed 4 years ago
Oh yeah thats a bug. Thanks for filing this issue. I will have to think about how to fix this. In the meantime I would recommend using jq or something to create a new JSON object to avoid this problem
@lawrencegripper I added support for complex nested JSON. I also fixed the weird bug you were getting. Let me know what you think.
Awesome, thanks - I got things playing nice with the jq workarond and I'll try and give the PR a spin today.
Released as part of v1.1.0. If there is a bug please file a new issue.
Thanks, sorry about not checking yesterday my days are a bit more confused than normal at the moment.
Had a play this morning and it worked well! Awesome work and thanks for the super quick fix!
Hi,
First up, awesome work on the provider it's super useful!
I've got a scenario where the
read
is returning a complex object like the below. It looks like the json string detection picks the last valid json string so you end up with just{"spark.speculation": true}
in the state file.Not sure if this is me doing something wrong, will carry on playing.
Full logs
State file