Currently we have some hacky parameters, like cirrusUseCompletionSuggester=no, which are not officially supported by the API but let users get slightly different result sets. Create a profile parameter for the api and allow the api users to explicitly select this rather than having an undocumented parameter.
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T122260 [GOAL] Promote related pages to production (on for everyone) on all wikis | |||
Resolved | ovasileva | T135030 [GOAL] Roll related pages from beta on mobile web for most wikis | |||
Resolved | debt | T128822 Add method for more like api query to not boost pages by popularity | |||
Resolved | dcausse | T132477 Create search engine profiles to allow api users to select specific search features |
Event Timeline
Comment Actions
Change 280634 had a related patch set uploaded (by EBernhardson):
Expose SearchEngine specific profiles
Comment Actions
Change 281468 had a related patch set uploaded (by EBernhardson):
[WIP] Allow user to customize search suggestion profile.
Comment Actions
Moving forwards this seems sensible, but how does this affect the old unofficial parameters? We need to continue to support them, as I've had to point them out to a few API consumers.
Comment Actions
Change 280638 had a related patch set uploaded (by DCausse):
Expose search engine profiles to SearchEngine
Comment Actions
Change 281468 merged by jenkins-bot:
Allow users to customize search suggestion profile