-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Update the TSV emitter-output-dir rule as required #37651
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
Conversation
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should only enable this rule as required if we know it is passing on everything in main and the private RPSaaSMaster. |
JS failure is un-relevant to this change and it is introduced by our feature gap Azure/autorest.typescript#3391 and the support is in progress. |
@weshaggard we have two separated prs to update all tspconfigs in the main and private RPSaaSMaster. The TypeSpec validation for all should be passed. Before switching to Please note JS has an known issue so one generation failed. @weidongxu-microsoft @msyyc @tadelesh @live1206 please help review from your language side. Thanks! |
I've removed the optional logic in TspConfigJavaAzEmitterOutputDirMatchPatternSubRule and TspConfigJavaMgmtEmitterOutputDirMatchPatternSubRule |
…in tspconfig.yaml
Update the TSV emitter-output-dir rule as required. Before switching to emitter-output-dir the relevant rules are optional for .Net and required for rest languages. The pr is to restore the status as it is.