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

improve matching filter error message #7578

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

Weiko
Copy link
Member

@Weiko Weiko commented Oct 10, 2024

Context

This can be thrown when a type is not properly supported by isRecordMatchingFilter. This should not happen but for some workspaces with legacy types this should help debugging.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR enhances the error handling in the isRecordMatchingFilter function by providing more detailed error messages for unsupported field types.

  • Improved error message in packages/twenty-front/src/modules/object-record/record-filter/utils/isRecordMatchingFilter.ts now includes the specific field type causing the error
  • This change aids in debugging issues related to unsupported field types, particularly beneficial for workspaces with legacy types
  • Enhanced developer experience by offering more precise information when encountering errors in record filtering

1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

@charlesBochet charlesBochet merged commit 1746343 into main Oct 10, 2024
13 checks passed
@charlesBochet charlesBochet deleted the c--improve-matching-filter-type-error-message branch October 10, 2024 16:58
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.

2 participants