Clarify TypeSpec code generation doc to emphasize preference for Modular #36446
Conversation
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
timovv
commented
Nov 5, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation for generating code from TypeSpec, specifically clarifying the guidance around the is-modular-library configuration option. The changes emphasize that Modular libraries should be the default choice unless explicitly directed otherwise by the Azure SDK Architecture Board.
- Simplified and strengthened the guidance for using Modular libraries over RLC
- Added explicit instruction that RLC generation requires Architecture Board approval
MaryGao
approved these changes
Nov 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.