OpenAPITools / OpenAPITools/openapi-generator
[REQ] Update boundary for http package in dart generator
Nobody has claimed this yet.
- 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.
The dependency section from the pubspec.yaml file of the dart generator is looking like that:
dependencies:
http: '>=0.13.0 <0.14.0'
intl: any
meta: '^1.1.8'
Since May 2023 the version 1.0.0 and higher is available for the http package. But I can't use newer http versions due to the upper boundary specified from the openapi-generator.
Describe the solution you'd like
I'd like to remove the upper boundary so that the newer version of the http package can be used.
dependencies:
http: '>=0.13.0'
intl: any
meta: '^1.1.8'
I have checked the http package version 1.2.1 and it was working without issues on my project.
Describe alternatives you've considered
Possible workaround is e.g. using a dependency-override in the app's pubspec.yaml file or manually modify the pubspec.yaml of the generated project.
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
Find the Dart generator's pubspec.yaml dependency section and inspect the existing http constraint. Update it to allow the requested newer versions, then verify that a generated Dart project's dependency declaration accepts http 1.x; no specific test file is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100