[AI-BUILDER-18] refactor: remove isFormMode#1437
Merged
kevinkim-ogp merged 1 commit intotrunk/aifrom Mar 10, 2026
Merged
Conversation
This was referenced Mar 4, 2026
Contributor
Author
2 tasks
This was referenced Mar 4, 2026
This was referenced Mar 6, 2026
pregnantboy
approved these changes
Mar 9, 2026
3 tasks
3 tasks
Contributor
Author
Merge activity
|
f9bb19e to
e4a71d7
Compare
kevinkim-ogp
added a commit
that referenced
this pull request
Mar 10, 2026
### TL;DR Removed the `isFormMode` parameter and form-based UI components from the AI builder workflow. ### What changed? - Removed `isFormMode` boolean parameter from GraphQL schema, mutations, and all related components - Deleted `AIFormModalContent` component and `ModifyPromptModal` that provided form-based workflow creation - Removed form input handling logic and related state management from AI builder context - Updated test cases to use chat-based prompt format instead of form mode - Simplified navigation state by removing form-specific parameters - Removed conditional UI rendering based on form vs chat modes ### Test 1. Navigate to the AI builder from the flows page 2. Test workflow generation using the chat input method - [ ] Confirm that existing chat-based workflow creation still functions correctly - [ ] Run the updated test suite to ensure all AI step generation tests pass
This was referenced Mar 11, 2026
This was referenced Mar 18, 2026
kevinkim-ogp
added a commit
that referenced
this pull request
Mar 26, 2026
### TL;DR Removed the `isFormMode` parameter and form-based UI components from the AI builder workflow. ### What changed? - Removed `isFormMode` boolean parameter from GraphQL schema, mutations, and all related components - Deleted `AIFormModalContent` component and `ModifyPromptModal` that provided form-based workflow creation - Removed form input handling logic and related state management from AI builder context - Updated test cases to use chat-based prompt format instead of form mode - Simplified navigation state by removing form-specific parameters - Removed conditional UI rendering based on form vs chat modes ### Test 1. Navigate to the AI builder from the flows page 2. Test workflow generation using the chat input method - [ ] Confirm that existing chat-based workflow creation still functions correctly - [ ] Run the updated test suite to ensure all AI step generation tests pass
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

TL;DR
Removed the
isFormModeparameter and form-based UI components from the AI builder workflow.What changed?
isFormModeboolean parameter from GraphQL schema, mutations, and all related componentsAIFormModalContentcomponent andModifyPromptModalthat provided form-based workflow creationTest
Confirm that existing chat-based workflow creation still functions correctly
Run the updated test suite to ensure all AI step generation tests pass