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

Tcgc/xml encoded name #1862

Open
wants to merge 3 commits into
base: release/november-2024
Choose a base branch
from
Open

Conversation

iscai-msft
Copy link
Contributor

@azure-sdk
Copy link
Collaborator

All changed packages have been documented.

  • @azure-tools/typespec-client-generator-core
Show changes

@azure-tools/typespec-client-generator-core - feature ✏️

add isPagedResultModel helper function

@azure-tools/typespec-client-generator-core - feature ✏️

add disableUsageAccessPropagationToBase to support language that does not generate base model

@azure-tools/typespec-client-generator-core - fix ✏️

do not add protocol usage for protocol method's response type

@azure-tools/typespec-client-generator-core - fix ✏️

have .serializedName take into account @Xml.name decorators

);
// 1. Check xml name encoding
if (xmlNameDecorator.length > 0) {
return xmlNameDecorator[0].arguments["name"];
Copy link
Member

Choose a reason for hiding this comment

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

So we're thinking that there really shouldnt be a case where encodedName is used with this decorator, right? We'll always return what's in @xml.name

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website 📚 Next docs

@tadelesh
Copy link
Member

as i mentioned in the meeting, please hold this fix until i get the design for serialization refactor in tcgc, thanks.

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.

4 participants