Design pattern for `next`, `previous`, and `updates` endpoints

anomaly / gallagher

The missing toolkit for extending Gallagher Command Centre, featuring a CLI, SQL interface, TUI and a Python idiomatic SDK

https://anomaly.github.io/gallagher/

MIT License

11 stars 2 forks source link

Design pattern for `next`, `previous`, and `updates` endpoints #24

Closed devraj closed 2 months ago

devraj commented 8 months ago

The library now uses async methods, hence we should be able to design a nice pattern that allows us to follow next, previous, and updates endpoints.

These are available as part of a response, hence we should be able to ask the response to follow the responses in either direction.

The real challenge here is that the URLs are dynamically generated so we have to discover the URLs once the original response is received.