-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Allow use of AI fields in view calculations. #15325
Allow use of AI fields in view calculations. #15325
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
…allow-ai-column-to-be-used-in-view-calculations
…mment for the next person to stumble on this.
…allow-ai-column-to-be-used-in-view-calculations
@@ -123,7 +123,7 @@ export interface AIFieldMetadata extends BaseFieldSchema { | |||
operation: AIOperationEnum | |||
columns?: string[] | |||
column?: string | |||
categories?: string[] | |||
categories?: string |
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.
Why this change? Is this a comma separated string or something like this, now?
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.
It has always been comma separated. It being a string array on the type was a mistake.
…allow-ai-column-to-be-used-in-view-calculations
Description
This PR allows you to group by AI field types in calculation views.
In the process of working on this, I noticed we're calling out to the LLM twice when saving a row, so I've removed the duplicate work.
Companion pro PR: https://github.com/Budibase/budibase-pro/pull/350/files
Addresses
Launchcontrol