swagger-api / swagger-api/swagger-codegen
[PowerShell] Enhancements to PowerShell generator
Nobody has claimed this yet.
- Dominant language
- Mustache
- Stars
- 17.8k
- Forks
- 6k
- PR merge metrics
- No merged PRs in 30d
Description
Description
Here are some enhancements for the PowerShell generator:
- Option to specify
ClientPath(which is hard coded to "$ScriptDir....\csharp\SwaggerClient" at the moment" - Integration tests using AppVeyor (similar to other API clients, we want to perform testings with the Petstore server (local) to ensure nothing breaks after changes)
- Review authentication support: HTTP basic, API key, OAuth2
- Add auto-generated documentation for API endpoints and models
- Update auto-genreated test files (APIs, models)
- Review README.md to see if the installation instruction, etc are clear
Swagger-codegen version
Latest master
Suggest a Fix
If anyone wants to work on these enhancements or have other suggestions on making the PowerShell generator better, please reply to let us know.
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 by reviewing the PowerShell generator and the existing generated test files, then compare its integration-test setup with the other API clients using the local Petstore server and AppVeyor. Use README.md and the listed authentication areas to divide the work into scoped tasks; done means the selected enhancements are implemented and the relevant generated tests, documentation, and checks are updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100