Azure Core linter rules docs and cleanup - Pass 2 #1545
+418
−170
Conversation
This file contains 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
|
All changed packages have been documented.
Show changes
|
timotheeguerin
requested review from
bterlson,
markcowl and
allenjzhang
as code owners
timotheeguerin
force-pushed
the
linter-rules-docs-2
branch
from
42d9a76
to
e540fc0
Compare
|
You can try these changes here
|
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.
Add documentation for the following rules and cleanup(remove the
Azure.service name filter and some other legacy filter from before using the linting engine)casing-stylemissing-operationrequire-auth: Flag missing@useAuthoperation-names: This one flagged a lot of our samples that usedcreateOrUpdateas the name of theResourceCreateOrReplaceoperation