Currently, when we encounter an array type and when trying to access the subtype by doing items.get('type') it throws as the postgres-tapoutputs theitemswith a json $ref pointer which can be found in the catalogues definitions. eg we expectitems[{ type: 'string' }]but actually receiveitems[{ $ref: }]`
I'd expect that singer's message parsing function would use jsonref or a similar to load the references for the target. Unless you can think of a reason not to do that I'll open an issue on the core singer lib and link back to this.
In the meantime, we could look for a $ref and resolve it our selves. Although this approach is probably error-prone.
Currently, when we encounter an
arraytype and when trying to access the subtype by doingitems.get('type') it throws as thepostgres-tapoutputs theitemswith a json $ref pointer which can be found in the catalogues definitions. eg we expectitems[{ type: 'string' }]but actually receiveitems[{ $ref: }]`I'd expect that singer's message parsing function would use
jsonrefor a similar to load the references for the target. Unless you can think of a reason not to do that I'll open an issue on the core singer lib and link back to this.In the meantime, we could look for a
$refand resolve it our selves. Although this approach is probably error-prone.