JSON-Elements with no children (hence, no values) causes failure of import about obsidian-import-json HOT 2 CLOSED

I can see the issue, in that the first element of the pack.provinces array contains the numeric value 0 instead of an object.

Whilst that is technically a valid JSON array, it doesn't seem sensible to have an array where one element is a number and the remainder of the elements are objects.

It looks like this also applies to the pack.features array.

Whilst the first object of th epack.burgs array is an empty object.

Whilst I could add some extra logic to simply ignore any elements which are not a JSON object, the better solution would be for the web site which is generating the data to produce a sensible array of data in the first place.

from obsidian-import-json.

I thought along the same lines. I will reach out to Azgaar and see if it can be updated.

For the time being, it's easy enough to manually add in a placeholder element to allow the importer to do its job.

Thanks.

from obsidian-import-json.