swagger-api / swagger-api/swagger-client

List cases where cacheing is good vs bad in the resolver

Open
#1,001 6 comments 0 reactions 2 assignees View on GitHub

@ponelat is already working on this.

Since Apr 21, 2017.

cat: resolver P2 type: discussion version: 3.x
Dominant language
JavaScript
Stars
2.7k
Forks
765
Avg merge
1d 1h
Merged PRs (30d)
6

Description

We need to establish a cacheing policy that is safe and explicit ( and tested )

  • Don't cache any try-it-out or arbitrary requests
  • Cache http requests within a single resolver invocation
  • Allow holding onto a cache across multiple resolver invocations ( ie: external cache management ).

ping @fehguy @webron @buunguyen please ensure the list above it accurate. Once it is we can implement the tests ( and the implementation too ).

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.