Open
Conversation
Contributor
|
No changes needing a change description found. |
Collaborator
|
You can try these changes here
|
lmazuel
reviewed
Mar 16, 2026
lmazuel
approved these changes
Mar 16, 2026
Member
lmazuel
left a comment
There was a problem hiding this comment.
Reviewed the array part, LGTM
catalinaperalta
approved these changes
Mar 17, 2026
Member
catalinaperalta
left a comment
There was a problem hiding this comment.
lgtm, this clarifies a lot of the xml behavior in typespec, the specific examples are really helpful. Same as Laurent mentioned, just to be extra sure to avoid confusion all property and target model names should be different so the docs are clear and easier to understand.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.