-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add Singular StandardFacet #370
Conversation
This change adds a singular StandardFacet that can be used to override facets rendered in Facets. J=BACK-2221 TEST=auto,manual Ran `npm run test` and confirmed all tests pass. Manually added a StandardFacet with Facets on the people's page under test-site/. Confirmed the facet gets overridden correctly.
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.
I think we want to talk through the plan, I don't think I did a good job of explaining what I was thinking in the items.
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.
LGTM, a couple of questions
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.
looks great! just two small comments
* @public | ||
*/ | ||
export function StandardFacet(props: StandardFacetProps) { return null; } |
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.
The general convention in this library is for each public component to be in its own file, along with the props and css classes in that file as well. Is there a reason behind this organization instead?
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.
I put it here since in the spec, they use <Facets.StandardFacet/>
. Let me know what you think!
# Version 1.3.0 ### Features - Introduce new Facet components including the new Facets (#360), StandardFacet (#370), NumericalFacet (#375), and HierarchicalFacet (#373) components which support more customizability than the previous Facet components. - Support the new RichTextV2 (Lexical) and Markdown fields which have been converted to HTML as FeaturedSnippetDirectAnswers (#379) - Remove the Yext logo from the search bar (#376) - Deprecate LocationBias (#338) component in favor of the new Geolocation component (#336) ### Bug fixes - Improve the UX of the search bar when long autocomplete text is returned which includes the truncation of long text (#378)
This change adds a singular StandardFacet that can be used to override facets rendered in Facets.
J=BACK-2221
TEST=auto,manual
Ran
npm run test
and confirmed all tests pass.Manually added a StandardFacet with Facets on the people's page under test-site/. Confirmed the facet gets overridden correctly.