-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
[Search] Rename types for better SDK code #16039
Merged
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
fffc0b8
Rename types for better SDK code
Mohit-Chakraborty d543551
Merge remote-tracking branch 'origin/main' into mohitc/SearchSdkRenames
Mohit-Chakraborty 52fd4a9
Rename Speller and Captions search options
Mohit-Chakraborty 95c74c1
Reorder parameters to have consistency across APIs
Mohit-Chakraborty 9cd36f7
Remove 'SearchIndexer' prefix from projection selectors
Mohit-Chakraborty 5c34638
Change enum name AdlsGen2->AzureDataLakeStorageGen2
Mohit-Chakraborty 964d6b3
move additional .NET SDK renames to the REST spec
Mohit-Chakraborty 67ac832
Revert changes in KnowledgeStore which has GAed
Mohit-Chakraborty d034a2e
Revert changes in CustomEntityLookupSkill which has GAed
Mohit-Chakraborty 12451c8
Revert changes in SIKSBlobProjectionSelector which has GAed
Mohit-Chakraborty 7c332cd
Revert changes in SearchIndexerDataSourceType which has GAed
Mohit-Chakraborty 64569c4
Rename ignoreResetRequirements->skipIndexerResetRequirementForCache
Mohit-Chakraborty File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
Does
Type
add anything to this name? Most enums are better without an extraType
at the end.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.
You are right - in our discussion we only decided on
QueryAnswerType
rename for theAnswers
parameter.We have 3 params that are similar in nature and usage and it would be good to keep them consistently named -
Speller
->QuerySpellerType
,Answers
->QueryAnswerType
andCaptions
->QueryCaptionType
- all extensible enums.One pro of adding the suffix
Type
is that the param can otherwise be misunderstood as containing part of a result object. It is best illustrated forQueryAnswer
andQueryCaption
. We could leave the third asQuerySpeller
or tack onType
there too to make all 3 names closely grouped.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.
@tg-msft - what do you think?
Also, do you know how should I go forward with this PR with the validation errors regarding changes in an existing swagger? Do I need to send an email, or can I tag folks here?