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

Add back AI POC support as it was in GUI1 #9313

Closed
Tracked by #9179
AdRiley opened this issue Mar 7, 2024 · 4 comments · Fixed by #9476
Closed
Tracked by #9179

Add back AI POC support as it was in GUI1 #9313

AdRiley opened this issue Mar 7, 2024 · 4 comments · Fixed by #9476
Assignees
Labels
-gui d-hard Difficulty: significant prior knowledge required p-high Should be completed in the next sprint x-new-feature Type: new feature request
Milestone

Comments

@AdRiley
Copy link
Member

AdRiley commented Mar 7, 2024

  • This is a first step in restoring AI functionality.
  • Internal feature only.
  • Enabled by adding environment variable with OpenAI key.

Activated by typing AI the component browser followed by the AI prompt.
On pressing enter the CB stays open and the code is replaced with the response from the AI model.

@AdRiley AdRiley added x-new-feature Type: new feature request -gui labels Mar 7, 2024
@AdRiley AdRiley added this to the Beta Release milestone Mar 7, 2024
@farmaazon
Copy link
Contributor

There are some details to be settled.

First, the AI POC I remember from GUI1 worked only for tables, so to work, the user needed to select a table node first. In GUI2, that would propagate input with operatorXXXX. (As #9210 is not planned yet). So I guess typing AI and prompt will leave input like operator1234.AI give me top 5 sales of every month, please. Are we ok with that?

@AdRiley
Copy link
Member Author

AdRiley commented Mar 7, 2024

  • Yes OK if it only works for tables for this story.
  • Yes OK for the activating command to be operator1234.AI give me top 5 sales of every month, please

@farmaazon farmaazon added d-hard Difficulty: significant prior knowledge required p-high Should be completed in the next sprint labels Mar 7, 2024
@farmaazon farmaazon self-assigned this Mar 18, 2024
@enso-bot
Copy link

enso-bot bot commented Mar 18, 2024

Adam Obuchowicz reports a new STANDUP for today (2024-03-18):

Progress: Ported the code from old GUI, so far in a bit dirty manner. It should be finished by 2024-03-29.

Next Day: Next day I will be working on the same task. fix all issues, and clean up code. Then add some features like "pending query" message.

@enso-bot
Copy link

enso-bot bot commented Mar 22, 2024

Adam Obuchowicz reports a new STANDUP for yesterday (2024-03-21):

Progress: Add tests and fixed all issues in GUI, but found some strange behavior in engine's extension methods. It should be finished by 2024-03-29.

Next Day: Next day I will be working on the same task. Apply a workaround for engine's issue and create a PR.

@mergify mergify bot closed this as completed in #9476 Mar 25, 2024
@mergify mergify bot closed this as completed in a6fc8cb Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-gui d-hard Difficulty: significant prior knowledge required p-high Should be completed in the next sprint x-new-feature Type: new feature request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants