Use consistent naming for API when used in a word #2465
Merged
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
|
Following you can find the validation results for the APIs you have changed.
You can validate these APIs yourself by using the |
l-trotta
approved these changes
Mar 26, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Mar 27, 2024
* Use consistent naming for API when used in a word * More renaming (cherry picked from commit 071b2f7)
l-trotta
pushed a commit
that referenced
this pull request
Mar 27, 2024
* Use consistent naming for API when used in a word * More renaming (cherry picked from commit 071b2f7) Co-authored-by: Sylvain Wallez <[email protected]>
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.
Renames
APIKeyQueryContainerandAPIKeyFiltersAggregationto use the same casing convention as the existingApiKey,ApiKeyAuthorization, etc.