-
Notifications
You must be signed in to change notification settings - Fork 0
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: searching issues in payload #387
base: main
Are you sure you want to change the base?
Conversation
…in order to allow searching in payload
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.
Two thoughts, but overall looks good! Let's ship it if it works 🚀
export async function up({ payload }: MigrateUpArgs): Promise<void> { | ||
const req = {} as PayloadRequest; | ||
|
||
const committeeMembers = await payload.find({ |
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.
Does this work without specifying a higher limit than default? I suspect there could be a limit here even with pagination false where it wouldn't apply to all items
await payload.update({ | ||
collection: NewsItems.slug, | ||
id: item.id, | ||
data: { |
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.
Hmm, this change for newsItems probably breaks localization in the admin UI and shows the last saved language version 🤔
It could be fine, but we could also make the field localized and save both locales here, but I wonder if that has even more implications for the search...
Description
When merging this, make sure to run the migration from the command line into prod!
Before submitting the PR, please make sure you do the following
Formatting and linting
pnpm format
and lint the project withpnpm lint