-
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
Ai fixes #14918
Ai fixes #14918
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
@@ -216,10 +216,6 @@ export async function inputProcessing( | |||
if (field.type === FieldType.FORMULA) { | |||
delete clonedRow[key] | |||
} | |||
// remove any AI values, they are to be generated |
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? Do we want to persist/analyse these imports?
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.
As I understood it, this was the thing stripping AI column results when doing a bulk import.
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.
that's it - when you re-import a CSV that has AI columns they were being stripped. We don't want to make the user generate them again, unless they specifically click to do so
Description
Some fixes for the AI functionality for v3. Importing an AI field from a table import caused empty values to be written, and the AI column functionality was not correctly wired up to our posthog feature flagging system.
Addresses