OpenAPITools / OpenAPITools/openapi-generator
[BUG] Javascript generated SDK
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 26.8k
- Forks
- 7.7k
- PR merge metrics
- PR metrics pending
Description
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue?
- Have you validated the input using an OpenAPI validator (example)?
- Have you tested with the latest master to confirm the issue still exists?
- Have you searched for related issues/PRs?
- What's the actual output vs expected output?
- [Optional] Sponsorship to speed up the bug fix or feature request (example)
Description
JavaScript generated SDKs do not include Intellisense for the built product. The un-built files in the src file include intellisense and work for autocomplete, but the dist folder after building does not.
openapi-generator version
5.0.0
OpenAPI declaration file content or url
N/A
Generation Details
Steps to reproduce
openapi-generator-cli generate -i /path/to/opeanpi.yaml -g javascript -o /path/to/outputfolder --additional-properties=usePromises=true
Related issues/PRs
https://github.com/OpenAPITools/openapi-generator/issues/1046
Suggest a fix
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
Start with the provided openapi-generator-cli command and compare the generated JavaScript SDK's src and dist folders after building. Confirm that the built dist output preserves the IntelliSense and autocomplete behavior present in src, using issue 1046 as related context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, openapi
- Domain
- api, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100