[http-client-rust] License generation for client Implementation

Open
#285 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
tooling

Research direction

Start by locating the Rust HTTP client generation path that emits Cargo.toml, then compare its license handling with the linked unbranded-license guidance. Done means custom-license clients use a manifest-relative license-file entry and generate the referenced LICENSE.txt rather than relying on license.workspace = true.

Written by the indexing model from the issue text.

Description

CodeGen Unbranded

Services can define custom licenses. See https://azure.github.io/typespec-azure/docs/howtos/generate-client-libraries/02package/#unbranded-license.

In this case, we should probably emit (or even update?) Cargo.toml to use a license-file with a manifest-relative path to the file we'd have to generate e.g., LICENSE.txt and not use license.workspace = true.

Dominant language
Rust
Stars
7
Forks
11
Avg merge
14h 15m
Merged PRs (30d)
6

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.

More from Azure/typespec-rust

All issues in Azure/typespec-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.