Skip to content

fix(template): name the Task entity file Task.jsonc to match its entity name - #638

Merged
davidsu merged 1 commit into
mainfrom
template_task_entity_file_case
Sep 23, 2026
Merged

davidsu merged 1 commit into
mainfrom
template_task_entity_file_case

Conversation

@davidsu

@davidsu davidsu commented Sep 23, 2026

Copy link
Copy Markdown
Contributor

Note

Description

The backend-and-client scaffolding template shipped its Task entity as task.jsonc while the schema inside declares "name": "Task". Because the Base44 platform derives an entity's identity from its filename, a freshly created project registered task as a second, distinct entity alongside Task. This PR renames the template file to Task.jsonc so the filename and the declared entity name agree.

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

  • Renamed packages/cli/templates/backend-and-client/base44/entities/task.jsonc to Task.jsonc (pure rename, file contents unchanged)
  • Updated the project-structure tree in packages/cli/templates/backend-and-client/README.md to show Task.jsonc
  • Added a Fixed entry to CHANGELOG.md under the unreleased section explaining the filename-derived entity behaviour

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 `docs/` (AGENTS.md) if I made architectural changes

Additional Notes

No source code under `packages/cli/src/` is touched — this is template + docs only, so no behavioural change to the CLI itself, only to what `base44 create` scaffolds. The remaining `task.jsonc` reference in `packages/cli/tests/cli/dev-security.spec.ts` is an inline fixture that test writes itself and is unrelated to this template. Existing projects already created from the old template are unaffected by this change and would need the file renamed manually.


🤖 Generated by Claude | 2026-09-23 10:26 UTC | 76ba6a7

…ty name

The platform derives an entity's name from the schema filename, while the CLI
reads the name field, so task.jsonc surfaced as a second entity beside Task
once the repo was opened in the editor.
@github-actions

Copy link
Copy Markdown
Contributor

🚀 Package Preview Available!


Install this PR's preview build with npm:

npm i @base44-preview/cli@0.1.17-pr.638.76ba6a7

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.1.17-pr.638.76ba6a7"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.1.17-pr.638.76ba6a7"
  }
}

Preview published to npm registry — try new features instantly!

@davidsu
davidsu merged commit 736213a into main Sep 23, 2026
15 checks passed
@davidsu
davidsu deleted the template_task_entity_file_case branch September 23, 2026 10:48
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