-
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
Update search vector configuration for Note #298
Comments
fyi @eliasylonen |
Do we agree here that we should keep the old rich text v1 body field while doing this custom command for fixing search on bodyV2, before we remove the V1 legacy field type, then at the end of all this migration process we'll remove everything v1 related, rename bodyV2 to body and remove everything related to V1/V2 ? So we may have a step when cleaning everything to rename the fields also in the search-related functions ? |
@lucasbordeau It sounds good to me. |
Moving the issue to core-team issues :) |
After we have replaced Note's body fieldMetadata with an enhanced version of it, we need to update the associated search vector configuration. It has to be done through a command as sync-metadata does not handle this usecase.
twentyhq/twenty#9850 (comment)
The text was updated successfully, but these errors were encountered: