Skip to content
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

Merged
merged 3 commits into from
May 12, 2023
Merged

Add Singular StandardFacet #370

merged 3 commits into from
May 12, 2023

Conversation

EmilyZhang777
Copy link
Contributor

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.

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.
@EmilyZhang777 EmilyZhang777 requested a review from a team as a code owner May 10, 2023 23:10
Copy link
Member

@benmcginnis benmcginnis left a 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.

src/components/FacetProps.tsx Outdated Show resolved Hide resolved
src/components/Facets.tsx Outdated Show resolved Hide resolved
src/components/StandardFacet.tsx Outdated Show resolved Hide resolved
@coveralls
Copy link

coveralls commented May 11, 2023

Coverage Status

Coverage: 84.635% (-1.2%) from 85.878% when pulling d445536 on dev/standard-facet into 4245636 on develop.

Copy link
Member

@benmcginnis benmcginnis left a 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

src/components/Facets.tsx Show resolved Hide resolved
src/components/StandardFacetContent.tsx Show resolved Hide resolved
Copy link
Member

@cea2aj cea2aj left a 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

src/components/FacetProps.tsx Outdated Show resolved Hide resolved
* @public
*/
export function StandardFacet(props: StandardFacetProps) { return null; }
Copy link
Member

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?

Copy link
Contributor Author

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!

@EmilyZhang777 EmilyZhang777 merged commit 9597e9a into develop May 12, 2023
@cea2aj cea2aj mentioned this pull request Jun 29, 2023
cea2aj added a commit that referenced this pull request Jun 29, 2023
# 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants