Resolve Parent Values early when their elements are children

Open
#5 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
api

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.

Description

enhancement

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.

  • Game -> Category -> Game
  • Series -> Game -> Series
  • Category -> Record -> Category
  • Category -> Record -> Game
  • Game -> Record -> Game
  • Game -> Record -> Category
  • User -> Runs -> User
  • User -> Records -> User

Probably even more

Dominant language
C#
Stars
32
Forks
11
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LiveSplit/SpeedrunComSharp

All issues in LiveSplit/SpeedrunComSharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.