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

fix(recommend): remove unused trendingFacets props #1433

Merged
merged 3 commits into from
Dec 16, 2022

Conversation

marialungu
Copy link

Remove fallbackParameters and queryParameters given that the recommend API does not support these props.
🐛 : JIRA

.gitignore Outdated
@@ -6,3 +6,5 @@ dist
*.umd.js
yarn-error.log
.env

.idea/
Copy link

Choose a reason for hiding this comment

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

Make a separate PR for this

Copy link
Contributor

Choose a reason for hiding this comment

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

it probably should just be reverted actually, local files should be in a global gitignore

@codesandbox-ci
Copy link

codesandbox-ci bot commented Dec 15, 2022

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit e3e3692:

Sandbox Source
javascript-client-app Configuration

Copy link
Contributor

@Haroenv Haroenv left a comment

Choose a reason for hiding this comment

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

change itself looks legit

.gitignore Outdated
@@ -6,3 +6,5 @@ dist
*.umd.js
yarn-error.log
.env

.idea/
Copy link
Contributor

Choose a reason for hiding this comment

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

it probably should just be reverted actually, local files should be in a global gitignore

export type TrendingFacetsQuery = Omit<TrendingQuery, 'model' | 'facetValue'>;
export type TrendingFacetsQuery = Omit<
TrendingQuery,
'model' | 'facetValue' | 'fallbackParameters' | 'queryParameters'
Copy link
Member

Choose a reason for hiding this comment

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

At this point why have a shared TrendingQuery type if they differ so much?

According to the API endpoints:

  • Trending facets
    • facetName: required
  • Trending items
    • facetName: optional
    • facetValue: optional

Copy link

Choose a reason for hiding this comment

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

Yeah that's a good point

Copy link
Author

Choose a reason for hiding this comment

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

yeah, i wanted to do that in a separate PR, both for client and for the libs

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.

5 participants