Graphql API Request
- Dominant language
- Java
- Stars
- 2.4k
- Forks
- 940
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 160
Description
I'd really like to build a client driven by graphql subscriptions. I'd like to formalize the request/response data; and the game-state.
It's hard to follow the client code as there is alot of UI code cluttering things up. I'm not looking to build a full UI, I just want to be able to drive a game using standard graphql.
So if I was going to build something like this, where should I run it?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by mapping the existing client code, UI code, request/response data, and game-state handling, then determine where a GraphQL subscription client could run; done requires an agreed implementation scope and execution location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, java
- Domain
- api, backend-api-design, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100