Skip to content

Conversation

@RNViththagan
Copy link
Contributor

  • Implement ConnectorGeneratorTool to generate Ballerina connectors from OpenAPI specs
  • Add interactive UI for spec input (file upload, URL fetch, paste)
  • Support both JSON and YAML OpenAPI specification formats
  • Integrate with AI agent workflow for external API integrations
  • Add state machine events for connector generation flow
  • Parse OpenAPI specs and display endpoint/schema metadata
  • Generate typed Ballerina client modules via Language Server

Resolves wso2/product-ballerina-integrator#1966
Related to wso2/product-ballerina-integrator#780

- Implement ConnectorGeneratorTool to generate Ballerina connectors from OpenAPI specs
- Add interactive UI for spec input (file upload, URL fetch, paste)
- Support both JSON and YAML OpenAPI specification formats
- Integrate with AI agent workflow for external API integrations
- Add state machine events for connector generation flow
- Parse OpenAPI specs and display endpoint/schema metadata
- Generate typed Ballerina client modules via Language Server
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 20, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@RNViththagan RNViththagan marked this pull request as ready for review November 20, 2025 06:19
- Enforce temp directory usage: Remove workspace folder fallback logic
- Track all generated files: Include Ballerina.toml in modifiedFiles for workspace integration
- Simplify function signature: Remove redundant tempProjectPath return value
- Add early validation: Check for required parameters at tool entry point
- Remove unused import: Clean up workspace import from vscode

This ensures connectors are generated in the temp directory where the agent works,
and all files (spec + connector + Ballerina.toml) are properly integrated to the
workspace when task completion is approved.
Replace temp directory paths with workspace paths when integrating
Ballerina.toml files generated by Language Server.
@xlight05 xlight05 merged commit 06023a6 into wso2:feature-ai-design-mode Nov 22, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants