Refactor TiledClient to allow per-request state to be reused

Open
#80 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
32/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
graphql, rust
Domain
api, backend-api-design

Research direction

Locate TiledClient and its request-resolution call sites. Review how auth headers are assembled and passed to each method, then determine the existing per-request state boundary. Done means the state can retain default headers for reuse across a request without rebuilding and passing the header map to every client method.

Written by the indexing model from the issue text.

Description

We currently have to build a headermap from auth headers and pass it to every method on the client for every call when resolving a request.

It might be worth looking at moving the client per-request state and letting it store the default headers.

Dominant language
Rust
Stars
0
Forks
2
Avg merge
5d 4h
Merged PRs (30d)
2

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 DiamondLightSource/glazed

All issues in DiamondLightSource/glazed

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.