Support sort in ExtendedSearchUsage#5868
Merged
Merged
Conversation
Contributor
|
Following you can find the validation changes against the target branch for the API.
You can validate this API yourself by using the |
Member
Mhh, I wonder if this is intended and if we should really prefer |
flobernd
approved these changes
Jan 13, 2026
gmjehovich
pushed a commit
that referenced
this pull request
Apr 13, 2026
* Support sort in ExtendedSearchUsage * Switch to enum key * typescript-generator: fix lint * Remove all output changes to test automation
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
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.
Added by @davidkyle in elastic/elasticsearch#139530. I initially wanted to do this instead:
However, typescript-generator converts that to a
Recordwhich expects all keys to be present:elasticsearch-specification/typescript-generator/src/index.ts
Lines 129 to 132 in 696f1cd
Interestingly,
SingleKeyDictionaryusesPartialwhich makes validation pass, but that's wrong. Since search usage is highly dynamic instead, I've opted forstring.