feat(connectors): add ConnectorTypeRegistry to generated types

[Paveltarno]

Note

Description

This PR adds support for generating TypeScript types for connectors in the Base44 CLI. It extends the existing type generation system to include a ConnectorTypeRegistry alongside the existing EntityTypeRegistry, FunctionNameRegistry, and AgentNameRegistry. This allows developers to get type-safe autocomplete for connector types when using the Base44 SDK.

Related Issue

None

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Other (please describe):

Changes Made

• Added connectors parameter to GenerateTypesInput interface in src/core/types/generator.ts
• Updated generateContent() to include connectors in empty check and generate ConnectorTypeRegistry
• Modified generateTypesAction() in src/cli/commands/types/generate.ts to read and pass connectors from project config
• Added test fixture for connector types (tests/fixtures/with-types-resources/base44/connectors/slack.jsonc)
• Updated test assertions to verify ConnectorTypeRegistry generation
• Updated empty template message to mention connectors

Testing

• I have tested these changes locally
• I have added/updated tests as needed
• All tests pass (npm test)

Checklist

• My code follows the project's style guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have updated AGENTS.md if I made architectural changes

Additional Notes

This PR builds on the connector infrastructure introduced in the pavelta-connectors-1 branch. The type generation follows the same pattern as existing resource types (entities, functions, agents), ensuring consistency across the codebase.

---

_{🤖 Generated by Claude | 2026-02-12 17:47 UTC}

[claude]

README check ran. 3 issue(s) found and applied: added missing 'eject' command, added missing 'connectors push' command, fixed 'logout' description. README.md has been updated in this branch.

The base branch was changed.

[Paveltarno]

@claude rebase

[claude]

Claude finished @Paveltarno's task in 16s —— View job

---

Unable to Perform Rebase

I'm unable to perform git rebase operations due to my current capabilities. Rebasing requires complex git operations that are outside my scope of branch operations.

How to Rebase Manually

You can rebase this PR branch manually with these commands:

git checkout pr-236
git fetch origin
git rebase origin/main
git push origin pr-236 --force-with-lease

Note: Use --force-with-lease instead of --force for safer force-pushing, as it will fail if someone else has pushed commits to the branch.

Alternative Approach

If you'd like me to help with specific conflicts or issues after you've attempted the rebase, feel free to tag me again and I can assist with resolving merge conflicts or updating code.

---

[Paveltarno]

Claude finished @Paveltarno's task in 16s —— View job

Unable to Perform Rebase

I'm unable to perform git rebase operations due to my current capabilities. Rebasing requires complex git operations that are outside my scope of branch operations.

How to Rebase Manually

You can rebase this PR branch manually with these commands:

git checkout pr-236
git fetch origin
git rebase origin/main
git push origin pr-236 --force-with-lease

Note: Use --force-with-lease instead of --force for safer force-pushing, as it will fail if someone else has pushed commits to the branch.

Alternative Approach

If you'd like me to help with specific conflicts or issues after you've attempted the rebase, feel free to tag me again and I can assist with resolving merge conflicts or updating code.

@claude, why can't you rebase? what capabilites do you require?

[claude]

Claude finished @Paveltarno's task in 28s —— View job

---

Why I Cannot Rebase

Checklist:

• Explain git rebase requirements
• Explain current capabilities
• Provide context on limitations

---

The Technical Reason

Git rebase is a complex operation that requires:

1. Interactive conflict resolution - When rebasing, conflicts often occur that require human decision-making about which changes to keep, how to merge conflicting edits, and whether the resolution maintains the intended functionality.

2. Branch manipulation - Rebase rewrites commit history by replaying commits on top of a new base, which involves:

   • Checking out multiple branches
   • Applying commits one by one
   • Potentially reordering or squashing commits
   • Force-pushing the rewritten history

3. Contextual understanding of history - Understanding which commits should be preserved, reordered, or dropped requires deep context about the development history and intentions.

My Current Capabilities

I can perform these git operations:

• Create and commit changes to files
• Push commits to branches (non-force push)
• Create new branches
• View diffs and history
• Stage and commit files

What I cannot do:

• Perform branch operations like merge, rebase, cherry-pick
• Force push (which is required after rebase)
• Handle interactive conflict resolution during complex git operations
• Rewrite commit history

Why This Limitation Exists

The limitation is intentional for safety reasons:

• Prevents history corruption - Rebasing requires force-pushing, which can overwrite others' work if not done carefully
• Avoids complex conflict scenarios - Automated conflict resolution during rebase could introduce bugs or break functionality
• Maintains safe collaboration - My design focuses on additive changes (new commits) rather than destructive operations (rewriting history)

What You Can Do

For rebase operations, you'll need to:

1. Perform the rebase manually (as I described in my previous comment)
2. Handle any merge conflicts that arise
3. Verify the rebased code still works as expected
4. Force-push with --force-with-lease for safety

If you encounter specific conflicts or issues during the rebase, I can help you resolve them by making targeted commits to fix the conflicts!

---

[github-actions]

🚀 Package Preview Available!

---

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.0.31-pr.236.577a109

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.0.31-pr.236.577a109"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.0.31-pr.236.577a109"
  }
}

• 📦 Preview Package: @base44-preview/cli@0.0.31-pr.236.577a109
• 🔗 View this commit on GitHub

---

_{Preview published to npm registry — try new features instantly!}

[claude]

README check ran. 7 issue(s) found and applied: Updated command descriptions for create, deploy, link, logout, whoami, entities push, agents pull/push; added missing eject and connectors push commands. README.md has been updated in this branch.

[kfirstri]

fix lint issues