Repository navigation
[docs-sync] Update documentation for recent code changes - #15
Draft
github-actions[bot] wants to merge 1 commit into
Draft
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
…ement These decorators are only meaningful for the java and csharp emitters. The decorator-requires-scope validation (added in Azure#5119) warns when they are used without a java/csharp scope. Update docs to reflect this requirement and fix code examples to use proper scopes. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This branch has not been deployed
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.
Summary
Updates documentation to reflect code changes merged in the last 7 days on
Azure/typespec-azuremain.Changes
@convenientAPIand@protocolAPIdecorator docs (Azure/typespec-azure#5119)Commit
6aa25543added a newdecorator-requires-scopevalidation that warns when@convenientAPIor@protocolAPIis used without ajava/csharpscope. These decorators are only meaningful for the Java and C# emitters — other emitters ignore them.Updated
website/src/content/docs/docs/libraries/typespec-client-generator-core/reference/decorators.md:@convenientAPIand@protocolAPIsections clarifying they require a"java"and/or"csharp"scope@convenientAPI(false, "java")instead of@convenientAPI(false))Related commits
6aa25543— Adddecorator-requires-scopevalidation for@convenientAPIand@clientOption(Adddecorator-requires-scopevalidation for @convenientAPI and @clientOption Azure/typespec-azure#5119)