swagger-api / swagger-api/swagger-codegen

ConfigurationParameters accessToken is not used in the API

Open
#12,165 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description

In the configuration parameters accessToken is aviable but never used in the api

Swagger-codegen version

3.0.44

Swagger declaration file content or url

I dont own the swagger definition and iam not allowed to post it here.

Command line used for generation

Generated it from the online editor

Steps to reproduce

Use the online editor and generate a typescript-axios client

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 with the typescript-axios client generated by the online editor and trace how ConfigurationParameters is defined and consumed. Confirm whether accessToken is propagated into generated API requests, then add a focused regression test if the client’s test entry point is available. Done means generated clients use the configured accessToken for authentication.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.