plugin-flow-builder: split, rename and reorganize files and functions

[Iru89]

Description

Pure structural refactor of botonic-plugin-flow-builder across two commits: splits, renames, and relocates files and functions to reduce coupling, improve module boundaries, and align the internal API around BotContext instead of ActionRequest. No logic changes — only file organisation, import updates, and signature alignments.

Context

action/index.tsx was doing too much: it defined FlowBuilderContext, the getContext factory, filterContents, and the full getContents routing logic, all alongside the React component. This forced all action modules (fallback.ts, knowledge-bases.ts, payload.ts, etc.) to import shared types from the entry-point file, creating unnecessary coupling.

Additionally, getContents and the post-processing pipeline (filter → track → resolveAIAgent → handoff/botAction) were inlined inside botonicInit and executeConversationStart, making them harder to reuse and test independently.

Finally, structured-output/flow-builder-content.ts was buried inside action/ai-agent/, making it hard to discover and reuse from other modules.

Approach taken / Explain the design

Files moved / renamed

Before	After
action/ai-agent/index.ts	action/ai-agent-from-user-input.ts
action/ai-agent/structured-output/flow-builder-content.ts	structured-output/flow-builder-content.ts

New file: action/context.ts

Extracted from action/index.tsx. Contains the FlowBuilderContext interface and the getFlowBuilderActionContext factory (formerly getContext). All action modules now import FlowBuilderContext from ./context instead of ./index.

filterContents moved to filters/index.ts

Extracted from action/index.tsx and added to filters/index.ts, next to ContentFilterExecutor where it logically belongs.

Rename: getContentsByAiAgent → getContentsByAiAgentFromUserInput

Clarifies that this function only handles the user-input routing path, not all AI agent invocations.

Import updates

fallback.ts, first-interaction.ts, knowledge-bases.ts, payload.ts, flow-ai-agent.tsx, and types.ts updated to point to the new locations.

New file: action/get-contents.ts

The getContents routing function (first interaction → payload → AI agent → knowledge base → fallback) was extracted from action/index.tsx into its own file. Its signature now receives BotContext instead of ActionRequest:

export async function getContents(
  botContext: BotContext,
  contentID?: string
): Promise<FlowContent[]>

New static method: FlowBuilderAction.processContents

The repeated post-processing pipeline that appeared in both botonicInit and executeConversationStart is now a single reusable method:

static async processContents(
  botContext: BotContext,
  contents: FlowContent[]
): Promise<FlowContent[]> {
  const filteredContents = await filterContents(botContext, contents)
  await FlowBuilderAction.trackAllContents(botContext, filteredContents)
  await FlowBuilderAction.resolveFlowAIAgentMessages(botContext, filteredContents)
  await FlowBuilderAction.doHandoffAndBotActions(botContext, filteredContents)
  return filteredContents
}

ActionRequest → BotContext in static methods

executeConversationStart, botonicInit, trackAllContents, and doHandoffAndBotActions now all receive BotContext instead of ActionRequest. This removes the dependency on the React-layer type from the core action logic and makes the functions usable in non-React contexts.

Cleanup in action/index.tsx

Removed now-unused imports: INPUT, EMPTY_PAYLOAD, inputHasTextOrTranscript, getContentsByAiAgentFromUserInput, getContentsByFallback, getContentsByKnowledgeBase, getContentsByPayload.

Testing

The pull request...

• doesn't need tests because it is a pure file reorganisation with no logic changes (all existing tests continue to pass)

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.