OpenAPITools / OpenAPITools/openapi-generator

[REQ] [csharp-netcore] Allow setting CachingPolicy for RestSharp Requests

Open
#5,352 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement: Feature
Dominant language
Java
Stars
26.8k
Forks
7.7k
PR merge metrics
PR metrics pending

Description

Is your feature request related to a problem? Please describe.

To enable caching within the generated csharp-netcore Rest Client, the CachingPolicy must be set:
https://github.com/restsharp/RestSharp/issues/401

Please open access to be able to pass the CachingPolicy to RestSharps RestClient.

Describe the solution you'd like

A property (CachingPolicy) in IReadableConfiguration which will be used inside request to construct the RestClient object.

Describe alternatives you've considered

Using the old swagger codegen project and manipulate the mustache template manually to use the RestSharp version > 105 (like released 2018) where CachingPolicy can be set. In the old swagger codegen version access to RestClient was public and was not constructed on every request.
Same as WebProxy access: https://github.com/OpenAPITools/openapi-generator/pull/4466

Additional context

Is there another mechanism to enable Caching?

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.

Research direction

Start by locating IReadableConfiguration in the csharp-netcore generator and the request path that constructs the RestClient; compare the referenced WebProxy access change. The issue names no files or tests. Done means CachingPolicy can be supplied through configuration and is used when constructing requests.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.