-
Notifications
You must be signed in to change notification settings - Fork 7
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
Date ordering preference for recipes #1704
base: main
Are you sure you want to change the base?
Conversation
…prioritise either relevance or date
…y. Always on when ordering with date, option for the user to force it 'always-on'.
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.
A couple of questions, but happy for you to merge!
@@ -45,6 +45,7 @@ interface WrapperProps { | |||
toolTipAlign: 'left' | 'center' | 'right'; | |||
urlPath: string | undefined; | |||
renderButtons: (renderProps: ButtonProps) => JSX.Element; | |||
noPinboard?: boolean; |
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.
Calling this noPinboard
feels like a bit of a double negative: noPinboard={true}
takes me a second to think about. Could we make it showPinboard
or enablePinboard
?
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 know what you mean.... the reason I did it like this is because the pinboard changes are nothing to do with me so it felt better to keep the "default" behaviour to show pinboard (as I don't know what else that may affect) and set the override to hide it rather than vice-versa
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.
You could have the prop default to true
if not specified, no?
case 'default': | ||
return undefined; |
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.
To be more explicit about how unknown values are handled, could we add a default case here?
case 'default': | |
return undefined; | |
case 'default': | |
default: | |
return undefined; |
); | ||
}} | ||
> | ||
<option value={'Relevance'}> |
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.
Using an uppercase R here feels inconsistent. I suppose it’s signalling that this option isn’t a field name? I think I’d still prefer lowercase.
What's changed?
FeedItem
Implementation notes
See the recipe-search-backend PR for an explanation of what "prefer" actually means
Checklist
General
Relevant tests added- None of the touched code currently has testsClient