|
Repo Added
|
Files
28
|
Badge
README BADGES
|
push
github
Merge master (v2.7.0) into develop (#323) * update Visitor to show visitorId max length * Support trusted publishing with OIDC (#308) J=WAT-5077 TEST=manual forked the repo to my personal git account. Verified that: - the `ci-verify-publish` script output the correct release tag - the `release` and `release:dry` scripts work as expected on a new patch, minor, major, alpha, beta, and custom version copied over the relevant changes from the forked repo. Verified that: - the `ci-verify-publish` script output the correct release tag - the `release:dry` script make the expected changes locally * Support facetAllowlist query parameter for vertical searches (#310) Allows the "facetAllowlist" parameter to be set on vertical searches. This parameter specifies the subset of field IDs that are configured as facet fields that facet options should be returned for in the search response. If unspecified, all fields configured as facetable can be returned if they have data for the given query. J=WAT-4928 TEST=manual Added a query to the test-site vertical requests that returns facets. Confirmed that the facetAllowlist parameter is settable and works as expected. * Undo version bump to 2.6.4 (#312) We have changed the release flow to be compatible with OIDC. * release: @yext/search-core@2.6.4 * Revert "release: @yext/search-core@2.6.4" This reverts commit d32e7625d. * release: @yext/search-core@2.6.4 * hotfix: fix release tag in trusted publishing workflow (#316) * release: v2.7.0-beta.0 * release: v2.7.0-beta.1 * chore: use reusable publish workflow (#320) * release: v2.7.0-beta.2 * release: v2.7.0 * rerun `npm i && npm run build` up to date, audited 921 packages in 1s 169 packages are looking for funding run `npm fund` for details 4 low severity vulnerabilities To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. --------- Co-authored-by: Kyle Gerner... (continued)
186 of 215 branches covered (86.51%)
Branch coverage included in aggregate %.
244 of 266 relevant lines covered (91.73%)
10.82 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|