Renaming filtering field to a shorter name#665
Merged
necusjz merged 1 commit intoAzure:mainfrom Dec 30, 2024
Merged
Conversation
necusjz
approved these changes
Dec 30, 2024
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
2 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.
The field length is expected to be less than or equal to 22. If the length is greater than 22, it fails a test in Azure-Cli repo.
So renaming enabled-filtering-criteria to filtering-criteria.
Note that this is a new change and the previously checkin long name is not rolled out to customer and it is not consumed in azure-cli too. Therefore, it is a non-breaking change.