I'm not sure about the lessons learned. Clearly somebody did a migration to move the data source on the UI for appoints from that call to something else, but d

I'm not sure about the lessons learned. Clearly somebody did a migration to move the data source on the UI for appoints from that call to something else, but didn't include removing the old way. From a rest-y-ness perspective, I think this would also show up as an API smell, of returning something that should be paginated as part of an API call whose purpose is to do something else. Design review should really have caught this