swagger-api / swagger-api/swagger-codegen

[Rust] Enhancements to Rust server generator

Open
#6,756 15 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Client: Rust Enhancement: General help wanted Server: Rust
Dominant language
Mustache
Stars
17.8k
Forks
6k
PR merge metrics
No merged PRs in 30d

Description

Description
  • rust2 is not a very informative name (renamed to rust-server via https://github.com/swagger-api/swagger-codegen/pull/6747)
  • Currently uses hyper 0.10 - work underway to upgrade to hyper 0.11 (which adds full async support)
  • Documentation on how to use the generated code in a Rust project is lacking
  • Consolidate the client generator with rust generator (rust-server generates both server and client code)
  • Add a means of testing rust-server's XML support back in (in a way that doesn't break everything else!). I believe other generators already do this, so it should not be over-hard.
  • The rust-server sample was generated from the pre-reversion petstore yaml. It should be re-generated from the current petstore yaml.
Swagger-codegen version

Latest master

Related issues/PRs

https://github.com/swagger-api/swagger-codegen/pull/6613

Suggest a fix/enhancement

If anyone wants to work on these tasks, please reply to let us know.

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

No files or tests are named. Start by reading the rust-server generator and related PR 6613, then choose one unchecked task, such as the hyper 0.11 upgrade, documentation, XML testing, or sample regeneration; done means that selected enhancement works without breaking the other generators.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.