You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks to me that the scanPosition endpoint returns the same information (although through a different implementation) as the frames endpoint.
Am I missing something? @psavery
The text was updated successfully, but these errors were encountered:
Yeah that is right. Originally, the GET /stem_images/{id}/frames was designed to return all frames, and the GET /stem_images/{id}/frames/{scanPosition} was designed to return just one frame.
However, because we added limit and offset to GET /stem_images/{id}/frames, you can now get one frame by specifying a limit of 1. So maybe GET /stem_images/{id}/frames/{scanPosition} is no longer needed. What do you think, @cjh1?
It looks to me that the
scanPosition
endpoint returns the same information (although through a different implementation) as theframes
endpoint.Am I missing something? @psavery
The text was updated successfully, but these errors were encountered: