Allow raw /rmeta output
tballison opened this issue · comments
The parse option uses /rmeta and then conflates all the keys together so that users can't tell which metadata goes with the primary file and which metadata goes with which embedded file.
Would it be possible to warn users of the current behavior and offer an option to get the raw json from the /rmeta endpoint?
will test/evaluate as part of the next release (not 1.24.2 which I will release today but ) 2.6.x which I will release next week.
Fixed in ca2a692