JSONAPI-Resources / JSONAPI-Resources/jsonapi-resources

Cache context based on record

Open
#930 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Ruby
Stars
2.3k
Forks
546
PR merge metrics
No merged PRs in 30d

Description

We allow access to certain fields on the user (email, etc.) only if context[:current_user] == record but this can't currently be used with caching in any reasonable manner.

For now I'm just caching a copy for each user who sees it, but that's absurd and definitely not what we need. Is there a better solution, or would it be possible to get the record inside Resource.attribute_caching_context(context)?

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.

Research direction

Start by reading Resource.attribute_caching_context(context) and tracing how context[:current_user] is used with caching. Compare this with the current per-user copy approach described in the issue. Done requires an agreed record-aware caching behavior, but the issue names no files, tests, or concrete acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
rails, ruby
Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.