• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

yext / answers-search-ui / 39496180107
63%
master: 63%

Build:
Build:
LAST BUILD BRANCH: develop
DEFAULT BRANCH: master
Ran 20 Oct 2026 08:57PM UTC
Jobs 1
Files 170
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

20 Oct 2026 08:55PM UTC coverage: 62.668% (+0.3%) from 62.388%
39496180107

push

github

web-flow
Merge master (v2.3.1) into develop (#2018)

* feat: add AI signpost for SearchBar (v2.2.0) (#2005)

This PR adds a new showAiSignpost boolean to SearchBar,
which if true, adds an AI tooltip to the searchbar

J=WAT-5883
TEST=auto, manual

Added tests. Ran test-site manually and saw signpost
as expected

* fix: up size limit for answers.min.js (v2.2.0) (#2007)

* fix: up size limit for answers.min.js (v2.2.0)

The bundle here is now just barely over the size limit
again, so up it by a little.

J=WAT-5883
TEST=manual

Was able to build bundle

* Automated update to THIRD-PARTY-NOTICES from github action's 3rd party notices check

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>

* release: v2.2.0

* feat: listener for yext:search-bar:close-autocomplete (#2010)

* add listener for close autocomplete

* npm run extract-translations

---------

Co-authored-by: Anh Thu Nguyen <anguyen@yext.com>

* release: v2.3.0

* feat: make focus-triggered autocomplete optional (#2013)

Before: focusing the search input requested suggestions, which could expand the dropdown before the user typed or clicked.
After: integrations can set autocomplete.openOnFocus to false to keep suggestions closed on focus. Typing and clicking still request suggestions, and autocompleteOnLoad still opens them when configured. The default remains true to preserve existing behavior.

J=WAT-5948
TEST=auto,manual

- added auto tests
- temporarily added `autocomplete: { openOnFocus: false }` to the Search Bar and confirmed autocomplete is triggered as expected on acceptance test fixtures

* fix: disable native automation for headless acceptance tests (#2016)

Chrome 155 acceptance runs hang with TestCafe's native automation, blocking release deployments. The test PR completed with native automation disabled and hung again when the flag was removed.

J=WAT-5949
TEST=compile

* release: v2.3.1

---------

Co-authored-by: Fondryext <160865254+Fondryex... (continued)

2105 of 3500 branches covered (60.14%)

Branch coverage included in aggregate %.

16 of 17 new or added lines in 2 files covered. (94.12%)

3589 of 5586 relevant lines covered (64.25%)

30.32 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
78.59
1.95% src/ui/components/search/searchcomponent.js
Jobs
ID Job ID Ran Files Coverage
1 39496180107.1 20 Oct 2026 08:57PM UTC 170
62.67
GitHub Action Run
Source Files on build 39496180107
  • Tree
  • List 170
  • Changed 2
  • Source Changed 2
  • Coverage Changed 2
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #39496180107
  • 1240d7f6 on github
  • Prev Build on develop (#36021329595)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc