Skip to content

Azure Core VNext and ClientCore updates - #7115

Merged
Srikanta (srnagar) merged 21 commits into
microsoft:mainfrom
srnagar:core-vnext
May 6, 2025
Merged

Srikanta (srnagar) merged 21 commits into
microsoft:mainfrom
srnagar:core-vnext

Conversation

@srnagar

Copy link
Copy Markdown
Member

No description provided.

@github-actions

Copy link
Copy Markdown
Contributor

No changes needing a change description found.

@azure-sdk

Azure SDK Bot (azure-sdk) commented Apr 24, 2025 •

Copy link
Copy Markdown
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 🛝 VSCode Extension

@weidongxu-microsoft Weidong Xu (weidongxu-microsoft) left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unblock.

There are a few things I have concern

  1. clientcore tests are disabled. It seems either the codegen or annotation processor have major problem (otherwise I'd expect just disabling a few test cases)
    • There be 1.0.0 compiler release at about May 4, we would likely need to release a working unbranded emitter on this version
    • We can merge this, and keep release unbranded emitter from feature branch on clientcore beta.5 for a few releases. But we'd expect the new clientcore work before long, as such release from branch would have large Eng cost (and likely would eventually fail when it diffs too much from main)
  2. Code around ClientMethod(Mapper/Template) have potentially large duplications. I'd hope we know what's the diff between the baseclass and subclass, so that is be possible to reduce the duplication in future.
  3. Turn of convenienceAPI would be a concern #7115 (comment)
  4. We want to avoid generating @Generated in mgmt #7115 (comment) (for now)

Comment thread cspell.yaml
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

emitter:client:java Issue for the Java client emitter: @typespec/http-client-java

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants