v1.0.1

Version 1.0.1

Fixes

• Addressed typos and inaccuracies in the README.
• Updated CircleCI configuration to publish folders for each major version in the CDN.

v1.0.0

Version 1.0.0

Changes

• Added TestCafe acceptance tests for the SDK.
• Added the ability for users to specify a custom Card type.
• Added a top-level noResults config object. This is used by both the MapComponent and VerticalResultsComponent.
• Updated some of the dependencies used to supply the SDK with polyfills.

Fixes

• Assorted fixes for the LegacyCard component. These fixes will improve IE11 styling and allow for bigDate to be specified.
• Assorted fixes for the CTAComponent. These fixes will promote backwards compatibility and improve styling.
• Styling fixes for the legacy AccordionResults component.
• Assorted fixes related to the 'No Results' case. In this case, the VerticalResultsComponent will not display applied filters. Additionally, the MapComponent can be configured to display all results for the vertical or not.

v0.13.2

Version 0.13.2

Changes

• Added analytics hooks for universal and vertical search events.
• Removed “note:“ prefix from the alternative verticals section of No Results.

Fixes

• Added aria-label to buttons in Pagination component for WCAG compliance; also update styling to properly align icons horizontally.
• Minor styling fixes for LegacyCard and AccordionCard to help with backwards compatibility.
• Added !default flag to all Answers SCSS variables that did not previously have it.

v0.13.1

Version 0.13.1

Changes

• Made all hard-coded strings in the various templates configurable.
• Updated the question submission endpoint hit by the SDK.
• Created a new UMD-style dist build of the SDK that includes polyfills.
• Added a LegacyCard component adapted ResultsItem.
• A new animation for the SearchBar component's icon.

Fixes

• Added an aria-label to the SearchBar component's input field for WCAG compliance.
• Assorted small styling fixes.
• Improved backwards compatibility with previous versions by making minor alterations to the interface of some components.

Version 0.13.0

This version contains breaking changes. When upgrading to this version, changes may be required to maintain the existing functionality of your experience.

Breaking Changes

• Updated styling for VerticalResults and Universal Results.
• Updated styling for the No Results screen, which appears when no results were found for a search.
• Removed the ‘templateUrl’ option in ANSWERS.init.
• You can no longer specify unescaped HTML for custom icons and DirectAnswers.

Non-Breaking Changes:

• VerticalResults now takes in a “card” config option - allowing per-result configuration, Calls To Action, and columns support.
• The No Results screen for VerticalResults can now be configured to display all possible results.
• Removed other instances of unescaped HTML from our templates.
• Updated Handlebars to v4.7.2

v0.12.2

Version 0.12.2

Changes

• Expanded unit test coverage.
• Polyfills are no longer stored in the global namespace.

Fixes

• Fixed the active navigation tab border in Safari.
• Fixed a race condition preventing multiple maps from getting initialized on the same page.

v0.12.1

Version 0.12.1

Changes

• Added the ability to send 1st party cookies to Analytics when conversion tracking is enabled.
• Added support for running the SDK against Sandbox.
• Created the SortOptions component.

Fixes

• Fixed the specificity of the Answers CSS reset.
• Pass sessionTrackingEnabled with all non-Analytics API requests.
• Fix flashing behavior of QuestionSubmissionComponent.
• Prevent Analytics event from firing twice on question submission.

Version 0.12.0

This version contains breaking changes. When upgrading to this version, changes may be required to maintain the existing functionality of your experience.

Breaking Changes

• Targeted CSS reset for the Answers SDK. This will not impact any custom styling added by the customers.
• Updates to the default styling of the SearchBar, AutoComplete, and SpellCheck components.
• Title is no longer included with the SearchBar component by default.

Non-Breaking Changes:

• More accurate analytics payload when SEARCH_CLEAR_BUTTON event occurs.
• The clear button appears in the SearchBar component when a user starts navigating through the AutoComplete options.
• Fixed IE11 bug in the logic determining if the SearchBar's input was focused.
• There is no longer the possibility for duplicate searches if the query has NEAR_ME intent.
• Fixed a bug preventing AutoComplete from working in the GeoLocationFilter component.
• Fixed issue with the DateRangeFilter and RangeFilter components that prevented the inclusion of these filters in queries by default.
• Improved WCAG compliance of SearchBar component.
• ErrorReporter prints out the full stack trace of the error in debug mode.

Version 0.11.0

This Version contains Breaking changes.
When upgrading to this version, changes may be needed to resume existing functionality.

Breaking Changes

• Q&A Component

  • Updated Configuration
  • Major changes to Template and Stylesheet
  • Major functional changes
  • Documentation

• Nav Component

  • Updated Configuration
  • Changes to Template and Stylesheet
  • Documentation

Non-Breaking Changes

• Enzyme for component testing

Version 0.10.1

Version 0.10.1

Changes

• LocationBias component
  • accept vertical key from search config
  • styling updates
  • Allow PersistentStorage to optionally replace state instead of pushing a new one when it updates history
• Q&A Submission Component Functional and Styling changes
• PersistentStorage
  • set URL update delay to 0
• Pass facet filter as field to empty array when no checkmarks
• Hide DirectAnswer, QASubmisison and LocaitonBias on loading
• Focus input on SearchComponent after using clear button
• Only show autocomplete dropdown when it is focused on query input
• Documentation
  • Add Search Configuration
  • Add Pagination Component
  • Update Q&A Submission Component

Fixes

• Do not show update location link after denying permission to location in the browser
• Make only one request (instead of two) for location data if user has already agreed to share location
• Ordering dependency between Facets and SearchBar
• Sample App
  • fix Facets
• AccordionResultsComponent: Fix for multiple accordion verticals