-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
re-export DA interfaces from search-core #131
Conversation
Pull Request Test Coverage Report for Build 2875962594Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
214dbea
to
7212ff3
Compare
@@ -7,7 +7,7 @@ it('can select a facet option', () => { | |||
const [initialState, facetOption] = createInitialState(false); | |||
const answers = createMockedHeadless({}, initialState); | |||
answers.setFacetOption('testFieldId', facetOption, true); | |||
expect(answers.state.filters.facets[0].options[0]).toEqual({ | |||
expect(answers.state.filters.facets?.[0].options[0]).toEqual({ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Out of curiosity did these TS issues come from a previous commit?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yup, I can see these TS issues when I switch to develop branch just now. Edit: the TS issue in integration/directAnswer.ts is from the version bump in this pr tho. Everything else come from previous commit
## Version 2.0.0 ### Breaking Changes - Re-exported all modified and newly added direct answer related interfaces from search-core V2. (#131 #133 #136 ) - More details of the changes are listed in [search-core v2 release notes](https://github.com/yext/search-core/releases/tag/v2.0.0) - Restructured static filters state to allow user to store more complex combination of static filters as well as field value filters. `SelectableFilter` interface is replaced with `SelectableStaticFilter`, which uses the new `StaticFilter` interface from search-core V2. The static filters state now accepts an array of `SelectableStaticFilter`. (#130 ) - All exports marked as `@deprecated` in previous version(s) as part of a rebranding process is now removed in V2 (#132 ) - for more details, the removed deprecated identifiers are listed in [v1.3 release notes](https://github.com/yext/search-headless/releases/tag/v1.3.0)
## Version 2.0.0 ### Breaking Changes - Re-exported all modified and newly added direct answer related interfaces from search-core V2. (#131 #133 #136 ) - More details of the changes are listed in [search-core v2 release notes](https://github.com/yext/search-core/releases/tag/v2.0.0) - Restructured static filters state to allow user to store more complex combination of static filters as well as field value filters. `SelectableFilter` interface is replaced with `SelectableStaticFilter`, which uses the new `StaticFilter` interface from search-core V2. The static filters state now accepts an array of `SelectableStaticFilter`. (#130 ) - All exports marked as `@deprecated` in previous version(s) as part of a rebranding process is now removed in V2 (#132 ) - for more details, the removed deprecated identifiers are listed in [v1.3 release notes](https://github.com/yext/search-headless/releases/tag/v1.3.0)
bump headless version to 2.0.0-alpha.131, to be publish after this pr is merged
J=SLAP-2324
TEST=none