Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http-specs, clientNamespace for java #771

Conversation

weidongxu-microsoft
Copy link
Member

@weidongxu-microsoft weidongxu-microsoft commented Nov 14, 2024

namespace override for Java

Otherwise the client would be generated under "client" package.

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 Nov 14, 2024

🦋 Changeset detected

Latest commit: 965efd3

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

@weidongxu-microsoft weidongxu-microsoft merged commit 7719b7a into Azure:main Nov 20, 2024
9 checks passed
@weidongxu-microsoft weidongxu-microsoft deleted the http-specs_clientNamespace-for-java branch November 20, 2024 02:16
@weidongxu-microsoft
Copy link
Member Author

will back port to typespec-azure with the PR to #758

github-merge-queue bot pushed a commit to Azure/typespec-azure that referenced this pull request Nov 26, 2024
backport Azure/cadl-ranch#771

After this, Java would start the migration to
http-specs/azure-http-specs and no longer update cadl-ranch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants