Skip to content
This repository has been archived by the owner on Jan 21, 2025. It is now read-only.

Add Rust to client naming scenarios #785

Merged
merged 1 commit into from
Dec 20, 2024

Conversation

jhendrixMSFT
Copy link
Member

Cadl Ranch Contribution Checklist:

  • I have written a scenario spec
  • I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
  • I have written a mock API
  • I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

Copy link

changeset-bot bot commented Dec 19, 2024

🦋 Changeset detected

Latest commit: 5560dd2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@azure-tools/cadl-ranch-specs Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@jhendrixMSFT jhendrixMSFT merged commit ef3b495 into Azure:main Dec 20, 2024
9 checks passed
@jhendrixMSFT jhendrixMSFT deleted the rust-client-names branch December 20, 2024 15:03
@tadelesh
Copy link
Member

tadelesh commented Dec 24, 2024

@jhendrixMSFT one thing to remind is you may also need to fix it in the new azure-http-spec here: https://github.com/Azure/typespec-azure/blob/main/packages/azure-http-specs/specs/client/naming/main.tsp.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants