Open eatyourpeas opened 1 month ago
I would be ideal to put in the body of the response with all the results but this would represent a breaking change for users
Could we add new top level fields with this so it's not a breaking change?
We have a typescript interface that matches the API specification of the Measurement class. If we add a new top level object might that not break it for people using older versions of the chart component?
Ah I see. Given it's a debugging option we could add it as a new always present field in the Open API spec and then as an optional field in the Typescript interface?
Now that multiple references are offered, there is currently no information in the response object either that the request was made or the reference that the return data corresponds to. I would be ideal to put in the body of the response with all the results but this would represent a breaking change for users, so the other option is to put it in the response header. Users can discard this, but also they can use this if they need.
FastAPI has this feature to add custom headers: