OpenAPITools / OpenAPITools/openapi-generator
`in: cookie` not properly handled by dart2 templates?
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Cookie authentication, I think (correct me if I'm wrong, please, as I'm still learning swagger/generator), is not handled correctly in dart2 templates. Rather than putting Cookie headers in requests back to server, the apiKey gets sent back as a query parameter.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect modules/openapi-generator/src/main/resources/dart2/api_client.mustache at the referenced line and trace how cookie authentication is rendered for an apiKey security scheme. Confirm the generated request behavior against the issue description; done means the apiKey is sent as a Cookie header rather than as a query parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100