LiveSplit / LiveSplit/SpeedrunComSharp
Resolve Parent Values early when their elements are children
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 32
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
If you query the categories of a game and query `category.Game` afterwards, there doesn't need to be a request anymore, as that is already known. The Caching algorithm might not catch that, as the game might've not been queried by it's ID initially, so the URL is different.
- [x] Game -> Category -> Game
- [x] Series -> Game -> Series
- [x] Category -> Record -> Category
- [x] Category -> Record -> Game
- [x] Game -> Record -> Game
- [x] Game -> Record -> Category
- [ ] User -> Runs -> User
- [ ] User -> Records -> User
Probably even more
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the caching algorithm and how related API resources are resolved after queries. Use the checked relationship chains as initial cases, then verify that querying a parent after its child requires no additional request; the remaining User relationships are also listed as unfinished scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100