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

Answers -> Search #243

Merged
merged 8 commits into from
Jul 20, 2022
Merged

Answers -> Search #243

merged 8 commits into from
Jul 20, 2022

Conversation

ElemelonWind
Copy link
Contributor

@ElemelonWind ElemelonWind commented Jul 19, 2022

Version 0.2.0-beta.243

@yext/answers-react-components is now @yext/search-ui-react!

Changes

Bugfixes

ElemelonWind and others added 2 commits July 19, 2022 11:33
* edited package.json and mentions of old name in readme

* test site renames

* fix typo
@coveralls
Copy link

coveralls commented Jul 19, 2022

Coverage Status

Coverage remained the same at 84.448% when pulling f658f80 on feature/answers-to-search into 7dbb88e on main.

ElemelonWind and others added 2 commits July 20, 2022 12:13
* renamed core imports

* replaced headless-react

* Automated update to THIRD-PARTY-NOTICES from github action's 3rd party notices check

* rename SearchCore.ts

* fixed capitlization of variables

* fix variable names

* test site package.json

* test site package-lock and nits

* fix renaming

* Automated update to repo's documentation from github action

* addressed more nits

* reverted package.json

* reverted packagelock

* test site packagelock

* packagelock updates

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
@ElemelonWind ElemelonWind marked this pull request as ready for review July 20, 2022 16:36
@ElemelonWind ElemelonWind requested a review from a team as a code owner July 20, 2022 16:36
@ElemelonWind
Copy link
Contributor Author

Coveralls is acting up :( Will rerun in an hour or so!

Copy link
Contributor

@nmanu1 nmanu1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you update the PR description with the changes?

@ElemelonWind
Copy link
Contributor Author

can you update the PR description with the changes?

I don't think anything other than the name (and the internal imports/variables) was changed, how should I say that?

@nmanu1
Copy link
Contributor

nmanu1 commented Jul 20, 2022

I don't think anything other than the name (and the internal imports/variables) was changed, how should I say that?

You can mention that headless-react was renamed, so now we have search-headless-react as a peer dependency instead of answers-headless-react

Copy link
Contributor

@nmanu1 nmanu1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're making a new beta version, the package.json version should be updated. And we probably want to add the other changes since the last beta version in the PR description/release notes

@ElemelonWind
Copy link
Contributor Author

If we're making a new beta version, the package.json version should be updated. And we probably want to add the other changes since the last beta version in the PR description/release notes

Where can I find all the other changes?

@nmanu1
Copy link
Contributor

nmanu1 commented Jul 20, 2022

Where can I find all the other changes?

If you look in the commit history for main, you can see all the commits since the last beta PR (#184) was merged in

@ElemelonWind
Copy link
Contributor Author

Where can I find all the other changes?

If you look in the commit history for main, you can see all the commits since the last beta PR (#184) was merged in

Updated, but I think it looks a bit messy- are there any that I don't need to mention?

@nmanu1
Copy link
Contributor

nmanu1 commented Jul 20, 2022

Updated, but I think it looks a bit messy- are there any that I don't need to mention?

For the CSS class interface updates, I don't think you need to list them all individually. Maybe just mention that we trimmed some of those interfaces and then list all the relevant PRs. You might also be able to group some of the fixes by component to make it more streamlined

@ElemelonWind
Copy link
Contributor Author

Updated, but I think it looks a bit messy- are there any that I don't need to mention?

For the CSS class interface updates, I don't think you need to list them all individually. Maybe just mention that we trimmed some of those interfaces and then list all the relevant PRs. You might also be able to group some of the fixes by component to make it more streamlined

edited!

@nmanu1
Copy link
Contributor

nmanu1 commented Jul 20, 2022

the latest commit on main (#248) should also be added in the description. it can be grouped with the third point under Changes about the StandardFacets count

@ElemelonWind
Copy link
Contributor Author

the latest commit on main (#248) should also be added in the description. it can be grouped with the third point under Changes about the StandardFacets count

Done :)

@ElemelonWind
Copy link
Contributor Author

Coveralls still isn't working :(

@nmanu1
Copy link
Contributor

nmanu1 commented Jul 20, 2022

I think these PRs would also be good to include in the description: #193, #201, #203, #205

@ElemelonWind
Copy link
Contributor Author

I think these PRs would also be good to include in the description: #193, #201, #203, #205

added!

@nmanu1
Copy link
Contributor

nmanu1 commented Jul 20, 2022

A couple more PRs to add: #194 and #198 (these can go with the other css trimming PRs), and #197 (also kind of related)

@nmanu1
Copy link
Contributor

nmanu1 commented Jul 20, 2022

Coveralls still isn't working :(

looks like they're having an outage: https://status.coveralls.io/

@alextaing
Copy link
Contributor

I think they're back up!

@ElemelonWind ElemelonWind merged commit 22960c4 into main Jul 20, 2022
@ElemelonWind ElemelonWind deleted the feature/answers-to-search branch July 20, 2022 19:33
yen-tt pushed a commit that referenced this pull request Sep 28, 2022
## Version 0.2.0-beta.243
`@yext/answers-react-components` is now `@yext/search-ui-react`!

### Changes
- Exported a string representing the content path to files in component lib that uses tailwind classnames. (#193)
- Trimmed/edited various CSS classes  interfaces. (#189, #190, #191, #194, #196, #197, #198, #200, #202)
- Made hovering over `FilterSearch` autocomplete suggestions trigger a highlight on the selected option and fixed its width/padding. (#203, #205)
- Removed `allowPagination` prop from `VerticalResults` (#217, #219)
- Updated `StandardFacets` to optionally display the number of results associated with each facet option. (#226, #248)
- Added a 'clear filter' feature for 'clear min and max' button in `RangeInput`. (#227)
- Added a range to the `ResultCount` that describes the range of results currently displayed by `Pagination`. (#228)
- Replaced `onSubmit` with `dropdownItemProps` in `RenderEntityPreviews` interface. (#225, #238)
- Separated recent searches in verticals to keep their recent search histories separate. (#242)
- Removed links from `AlternativeVerticals` and deleted `UniversalLink` interface. (#229)
- `@yext/answers-headless-react` has been renamed to `@yext/search-headless-react`, and has been replaced by such as a peer dependency. (#243)

### Bugfixes
- When `label` is undefined, `FilterSearch` does not display default 'filter' label (#201)
- Fixed `DropdownMenu` tabbing and selecting behavior (#206, #207)
- Fixed a bug where clicking the `ApplyFiltersButton` did not reset the pagination offset. (#213)
- Fixed linebreak bug in `resultsCount` (#218)
- Fixed a bug where range input static filters were removed when selecting/de-selecting facet options with different `fieldId`s. (#224)
- Fixed `LocationBias` mobile styling (#221)
- Fixed `ThumbsFeedback` issues of not having a default width and height, as well as rotation issue with the thumbs-down button. (#233)
- Fixed `inputPrefix` collision issue and tooltip location in `RangeInput`. (#232, #234)
- Fixed a bug where facets were not being reset when applying a filter from `FilterSearch` with `searchOnSelect=true`. (#236)
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.

None yet

5 participants