When making an API call to Tiled from a browser like table/partition/myTable/primary/internal?partition=0&format=application/json-seq the response varies depending on the number of rows.
ex) console.log(response.data)
Multi row table returns
data: '{"seq_num":1,"time":1778275162.685306,"diode_x_mm":17.19,"diode_x_mm_user_setpoint":17.19,"ts_diode_x_mm":1778185799.465803,"ts_diode_x_mm_user_setpoint":1778185799.465803}\n{"seq_num":2,"time":1778275163.186045,"diode_x_mm":17.19,"diode_x_mm_user_setpoint":17.19,"ts_diode_x_mm":1778185799.465803,"ts_diode_x_mm_user_setpoint":1778185799.465803}\n{"seq_num":3,"time":1778275163.4077709,"diode_x_mm":17.19,"diode_x_mm_user_setpoint":17.19,"ts_diode_x_mm":1778185799.465803,"ts_diode_x_mm_user_setpoint":1778185799.465803}\n{"seq_num":4,"time":1778275163.5238419,"diode_x_mm":17.19,"diode_x_mm_user_setpoint":17.19,"ts_diode_x_mm":1778185799.465803,"ts_diode_x_mm_user_setpoint":1778185799.465803}'
However for single row tables it's an object:
Single rows return
data: Object { seq_num: 1, time: 1778193890.6301696, diode_y_mm: 4, … }
diode_y_mm: 4
diode_y_mm_user_setpoint: 4
seq_num: 1
time: 1778193890.6301696
ts_diode_y_mm: 1778187424.480949
ts_diode_y_mm_user_setpoint: 1778187424.480949This will break any client that assumes it's a json sequence that needs to be parsed. This was observed specifically with data written with Tiled Writer from bluesky runs.
When making an API call to Tiled from a browser like
table/partition/myTable/primary/internal?partition=0&format=application/json-seqthe response varies depending on the number of rows.ex)
console.log(response.data)Multi row table returns
However for single row tables it's an object:
Single rows return
This will break any client that assumes it's a json sequence that needs to be parsed. This was observed specifically with data written with Tiled Writer from bluesky runs.