yext / search-ui-react / 24469789513

84%

main: 84%

Build Type

push

github

Committed by web-flow

Commit Message

Merge main (v3.0.1) into develop (#661)

* feat: allow users to turn analytics on and off (v2.1.0) (#632)

* feat: allow users to turn analytics on and off (v2.1.0)

This PR adds a new property to the SearchAnalyticsConfig, which
can be used to start with analytics enabled or disabled by
default. Three new methods are added to the analytics object-
two to turn analytics on/off, and one to get the current enabled
status.

J=WAT-5404
TEST=auto, manual

Ran test site locally with debugging and buttons to turn
analytics on and off, saw expected behavior.

* Update various names to be in-line with pages code

* Automated update to repo's documentation from github action

* Add enableYextAnalytics function to window

* drop unneeded parens

---------

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

* release: v2.1.0

* More accessbilities fixes for autocomplete results (#635)

* More accessbilities fixes for autocomplete results

Associate the visible label with the input via `label` + `htmlFor`, and wire `DropdownInput` with `inputId` and `aria-labelledby`.

Change the instructions container from `hidden` to `sr-only`, so `aria-describedby` references content that is actually exposed to screen readers.

J=WAT-5357
TEST=manual

tested with voice over enabled on test-site

* Update snapshots

---------

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

* release: v2.1.1

* chore: suppress error/warning spam, fix key errors etc (#642)

* fix: point TypeScript output to dist directory (#644)

* suppress error/warning spam, fix key errors etc

* set ts output dir to dist

* retry logic to WCAG

* release: v2.1.2

* fix: improve accessibility in FilterSearch and Facets (v2.2.0) (#638)

* fix linting; added optional region landmark semantics to FilterSearch

* Automated update to repo's documentation from github action

* chore: suppress error/warning spam, fix key errors etc (#642)

* ... (continued)

Coverage Stats

1070 of 1483 branches covered (72.15%)

Branch coverage included in aggregate %.

91 of 115 new or added lines in 7 files covered. (79.13%)

1 existing line in 1 file now uncovered.

2344 of 2559 relevant lines covered (91.6%)

124.32 hits per line