-
Notifications
You must be signed in to change notification settings - Fork 180
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
[LintDiff] Need separate ruleset for TypeSpec-generated Swaggers #7732
Labels
Central-EngSys
This issue is owned by the Engineering System team.
Spec PR Tools
Tooling that runs in azure-rest-api-specs repo.
Comments
Another proposed solution would be to allow the lintdiff command to accept a list of rules to ignore. This could be simpler to implement. cc/ @allenjzhang |
konrad-jamrozik
added
Central-EngSys
This issue is owned by the Engineering System team.
Spec PR Tools
Tooling that runs in azure-rest-api-specs repo.
labels
Feb 22, 2024
This was referenced Feb 24, 2024
This work is now completed. The raw log shows rules have been disabled for TypeSpec-generated specs:
but not for manually-written specs, e.g.:
We can also see the spec was recognized as TypeSpec-generated (
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Central-EngSys
This issue is owned by the Engineering System team.
Spec PR Tools
Tooling that runs in azure-rest-api-specs repo.
We need the following capabilities in LintDiff:
The mechanism will allow us to accomplish the following goals:
The text was updated successfully, but these errors were encountered: