List active sessions using the API about quilkin HOT 2 OPEN

Thank you for your issue!

This where I scope creep this feature a little bit and ask, instead of having dedicated endpoints for each kind of data users are interested in querying, what if we instead had a GraphQL endpoint, and we merged this with /config? That would also be more useful for your use-case where you could subscribe to sessions, and then you'd receive session data as it becomes available in Quilkin, rather than needing to repeatedly poll and search for new information yourself.

What do you think @markmandel ?

from quilkin.

I knew I was going to have to learn GraphQL one day 😄 runs off to read docs

Yeah, this makes a lot of sense, and it's expandable over time. We can put config info in here, session info, and potentially more -- and it can change depending on mode, since the endpoint has built in discover ability. Yeah, count me as sold.

I do wonder if /config is the right endpoint name (/graphql ?), but that's minor detail.

@XAMPPRocky got a favourite Rust + GraphQL library?

from quilkin.